In the past few years though, it’s been creeping into my domain too.
Even this needs a qualifier. Radiation exposure can cause bit flips. Certain aerospace applications must address this, and even some earth-bound applications at high altitude.
A quick AI-assisted search informs me that neither AMD nor Intel document any on-CPU error correction, though perhaps there is some. Apple currently has zero systems that even use ECC, which seems insane to me given they’re shipping systems with up to 512 GB of RAM.
This seems to be an issue that’s falling through the cracks again. I guess nothing will be done until there’s a critical failure due to a bit flip, and verifying that was the cause for a given problem is difficult.
On ECC, Apple needs to Think Different (tm). Maybe it should introduce actual “Pro” machines…
No matter what's trending worse there's always this thought terminating phantom law of conservation of everything. The fact that something is not an entirely new bespoke phenomenon always turns into denial that it could be happening more often or in a newly qualitatively worse way.
Now it’s somehow guarantied that the volume of dirtied quickly prompted version of anything anyone ever cherished far exceed the scarce outcomes of the original.
The actual programming logic has certainly always been complex, but the integrations weren't so bad. You could learn your very small toolset quickly and focus on ideas. Now, you have an ultra-massive toolchain to come to terms with, made up of free software and "cloud" architecture that starts off cheap and gets expensive later on.
Dependencies have always been the problem, but that problem has expanded in every direction, at every layer, approaching our own limits of comprehension. AI has allowed us to catch up, temporarily, but given the collective penchant for upping the ante, I expect the real supernova is yet to come.
Java via maven central is similar. It’s not a popular language. We know those libraries are riddled with issues - log4j’a big vulnerability isn’t that old - and simply requiring a GPG signature on a package is a thin guard against compromised uploads.
The NPM ecosystem is uniquely suited to supply chain attacks though. It has a massive rate of churn, which makes it impossible to maintain dependencies safely. You either lock in and hope there’s no big issues or ride the wave and hope you don’t get hit by zero days.
AI has allowed us to scale development effort massively - and shows the same weaknesses as scaling human teams too quickly - planning, verification/testing and code fragmentation become issues almost immediately.