esterna

(Un)Fortunately, finding someone who is "at fault" generally helps neither in investigating root causes nor in preventing similar problems in the future.

Usually it's detrimental, hence (criminal) investigations of personal liability in such cases are often only allowed after systemic investigation has concluded.

In court, you are allowed to withhold information that makes you look bad, which is simply lethally unhelpful when we want safer trains.

Of course, consumers don't intrinsically care about the bits. It would be more interesting to look at "price per website viewed/movie watched/game stored on your disk". Just like "time to open program" has worsened despite objective HW improvements, I'm not sure those metrics got any better.

I'm almost cynically happy about Moore's law ending and hardware getting expensive if this is what it takes to improve software in the long term.

Almost any moderation system working under consistent rules will be stable, because the people and topics disadvantaged by the moderation will simply leave your platform.

Silica uses femtosecond lasers for writing and supposedly mostly ordinary silicate glass as the medium. This would probably mean more costly drives and severely cheaper media (Folio claims $3/TB now, $1/TB eventually. I wager Silica would be at least 10x cheaper). If Silica keeps its promises, we might be looking at archival prices cratering. But it's been in development for over a decade, I wouldn't hold my breath.

Really interesting would be R/W speeds.

> All type parameters have an implicit bound of Sized. The special syntax ?Sized can be used to remove this bound if it’s not appropriate.

, which HashMap does not do, i.e. the keys and values have to have a statically known size.

This also applies to reading restaurant reviews before visiting. Or for that matter, reading any published book you outsource judgement to the publishing house (what books they pick up). Or, if you are easily convinced by jargon: Exploration has a non-zero opportunity cost.

Read the article. The elaborator (where metaprogramming is evaluated) is not part of the trusted computing base. The security model is that bad proof terms get rejected, not that they're never generated.

And it has array programming features, logging, and (time-travel!) debugging all intuitively graspable for most non-technical people.

I sincerely think there are lots of unlearned lessons in studying Excel.

There is one example that succeeded and became the most widely used programming paradigm on the planet: Spreadsheets

Though you might argue that the "programming language" part was rather accidental

> How's this any different than say, not bringing your wallet with you, because 95% of the time apple pay works

Apple Pay involves at least a third party (your bank) as a part of its function. This entity has to be reachable.

Unlocking my car needs me, and my car.

> when the payment terminal randomly decides to not accept apple pay?

I would be justified in being mad if, randomly, my BMW car would decide to not accept a BMW key (virtualized or otherwise).

> Not to mention there are plenty of other ways a phone can fail. It can [...]

"I will not accept this Euro bank note. You could have dropped it into the gutter on your way here, so it's strange for you to be mad at me if you don't have a backup."

Why should be? I think it is abundantly clear by now that market competition alone will not fix this. Though that does not stop people from claiming "Yes that failed and people suffered/died, but that was not real capitalism! If only we had a real free market, it would have been better!"

NIS2 allows for the arrest of managers in case of cybersecurity incidents resulting from negligence. I think it's a step in the right direction, but we'll have to see how it plays out.

Once I start a conversation about Postgres query plans, maybe 95% of the knowledge will be almost certainly not needed, and for an inference provider there will be many more concurrent queries with reasonably large overlap. Maybe future architectures will be able to take advantage of this so not all parameters are needed in memory for almost all instances.

If we are talking about all knowledge, then I agree that the compression ratio is very impressive already.

I wonder if the EU will someday figure out a patch for this "Deteriorate everyone's user experience in a way that is technically compliant and blame the EU" behavioural exploit...

Once once they are rejected by charities, they can be destroyed just like before this law. EU regulators are flawed humans, but you can be assured that any argument you can come up with in 10 minutes has been considered.