Hacker Newsnew | past | comments | ask | show | jobs | submit | inejge's commentslogin

> Capital "i"s without crossbars aren't capital "i"s. They're lower-case Ls. Any font that doesn't recognize this should be rejected.

You have asserted this at least thrice in the past thirty minutes. What makes you feel so strongly about it? "Rejected" for what purpose? Do you understand that you've just trashed Helvetica, to take a famous example?


What an odd question. I don't like degraded communication or stupidity. Is that enough justification?

Oh wait, I trashed hallowed Helvetica? The Lord's font? The font used on the tablets Moses carried down from Mount Sinai? OMG whatever shall I do.

Meanwhile, the question stands.


> The 80287 (AKA 287) and 80387 (AKA 387) floating point microprocessors started to pick up some competition from Weitek 1167 and 4167 chips and Inmos Transputer chips, so Intel integrated the FPU into the CPU with the 80486 processor (I question whether this was a monopoly move on Intel's part).

I don't think it was, transistor density became sufficient to integrate such a hefty chunk of circuitry on-die. Remember that earlier CPUs had even things like MMUs as separate chips, like Motorola 68851.


There's illiteracy, and there's functional illiteracy. They're not the same, and people often confuse the two. A literally illiterate person (ha!) wouldn't make headway with almost any realistic computer interface, icons or not.

The 20% statistic is about people who have great trouble reading and comprehending simple sentences, not discerning individual words. It's tragic and debilitating, but such people could muddle through a simple interface with textual labels. A truly illiterate person couldn't.


It's not remotely the same type of error -- error non-handling is very visible in the Rust code, while the Lua code shows the happy path, with no indication that it could explode at runtime.

Perhaps it's the similar way of not testing the possible error path, which is an organizational problem.


> I think it was Snowden who made TLS the default.

Snowden's revelations were a convincing argument, but I would place more weight on Google in its "we are become Evil" phase (realistically, ever since they attained escape velocity to megacorphood and search monopoly status), who strove to amass all that juicy user data and not let the ISPs or whoever else have a peek, retaining exclusivity. A competition-thwarting move with nice side benefits, that is. That's not to say that ISPs would've known to use that data effectively, but somebody might, and why not eliminate a potential threat systemically if possible?


Reading this it seems to me that ISPs missed a trick by not offering privacy features. These features were already baked into mobile wireless it probably wouldn’t have been a huge big deal for them to provide it. That’s what happens when you treat your business as a source of rent

It will help that side of the process (although, as a sibling has noted, you can CNAME your way into a better-controlled update service), but the challenge of automating cert changes for various non-HTTP services, including various virtual or physical boxes with funky admin interfaces, remains. I don't expect that vendors will do much about that, and it will end up on admins' plates, as usual. There will be much grumbling, but fewer solutions.

There are quite many solutions. For very funky systems, you can use a cert tied to a private CA. Then you can control the cert lifetimes. Or place them behind a reverse proxy that is easier to control.

"Code frequency" for jxl-rs shows no activity from Aug 2021 to Aug 2024, then steady work with a couple of spurts. That's both a longer hiatus and a longer period of subsequent activity (a year+ ago isn't "recently" in my book.) What data have you based your observation on?

my fallible memory of roughly the same sources

> On the SEU issue I’ll add in that even in LEO you can still get SEUs

As a sibling post noted, SEUs are possible all the way down to sea level. The recent Airbus mass intervention was essentially a fix for a badly handled SEU in a corner case.


Okay now I'm imagining a classical ballet recreation of the "Heeere's Johnny" scene. With firemen.

> What has always baffled me is how CS uses the word "safety" where all other industries use "robustness".

FWIW "safety factors" are an important part of all kinds of engineering. The term is overloaded and more elusive in CS because of the protean qualities of algorithmic constructs, but that's another discussion.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: