News for hackers. Stuff that matters.
Re:Software is breaking down at a systemic level by LPisGood on Monday November 16, 2026 @01:26PM (#50520971)
Software has always been broken at a systemic level. It’s a complicated continuously changing web of abstractions and abstraction breaking hacks attempting to survive prolonged contact with reality.
Re:Software is breaking down at a systemic level by SV_BubbleTime on Monday November 16, 2026 @01:30PM (#50521026)
I do embedded. I’ve always marveled at how ludicrous that “real software” is. I have truths. I have registers that will never be or act differently, I can make pretty damn good assumptions that no one will put this code somewhere else’s etc.

In the past few years though, it’s been creeping into my domain too.

Re:Software is breaking down at a systemic level by bumby on Monday November 16, 2026 @01:36PM (#50521112)
>I have registers that will never be or act differently

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.

Re:Software is breaking down at a systemic level by LPisGood on Monday November 16, 2026 @01:42PM (#50521202)
At high altitude or high deployment numbers. Hyper scaler data centers measure these “one in a million” anomalies in thousands of times per houe.
Re:Software is breaking down at a systemic level by leftnode on Monday November 16, 2026 @01:43PM (#50521213)
Yeah, don't we have error correcting RAM for this reason, here on Earth?
Re:Software is breaking down at a systemic level by Recurecur on Monday November 16, 2026 @02:30PM (#50521887)
Sure, but RAM isn’t the only place a bit can flip. Registers are a thing. IBM had error correction in Power architecture CPU registers, not sure where AMD, Intel, or Apple (lol) are on that issue. IIRC register bit flips first came up with Sun SPARC hardware, which Sun mitigated, but of course SPARC isn’t used too much these days…

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…

Re:Software is breaking down at a systemic level by marcosdumay on Monday November 16, 2026 @01:45PM (#50521234)
Besides, chip bugs are famous since the Pentium, and unreliable circuits are the normal way to describe circuits, you have to add notice when you get a reliable one.
Re:Software is breaking down at a systemic level by skydhash on Monday November 16, 2026 @01:49PM (#50521301)
That's why we do requirement gathering and analysis. Engineering is always about tradeoffs and things that matters in certain context don't in others. The issue is that in a lot of orgs, while there's a record of decisions, we don't usually track assumptions and the overall system is full of contradictions. Also there's no overall keeper of knowledge (either one person or a team) that periodically ensure that contradictions are kept at minimum.
Re:Software is breaking down at a systemic level by add-sub-mul-div on Monday November 16, 2026 @01:42PM (#50521199)
I don't get this thing where people are allergic to the idea that change can happen.

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.

Re:Software is breaking down at a systemic level by psychoslave on Monday November 16, 2026 @01:42PM (#50521200)
Well, yes, but the proportion of systemic level broken stuffs might have change a bit. Just like, ok, there was always rule34 lurking to make dirty everything innocent that remained of the untainted child memory one had.

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.

Re:Software is breaking down at a systemic level by kerblang on Monday November 16, 2026 @01:43PM (#50521216)
It was less broken before open source allowed an architectural explosion, because the dependencies were too expensive. It took a lot of arguing to get management to splurge on a single library or other tool. A lot of astronaut-architect wannabes were constantly grumpy about mgmt that wouldn't pay for the latest whiz-bang thingie.

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.

Re:Software is breaking down at a systemic level by cmiles74 on Monday November 16, 2026 @01:55PM (#50521395)
Is the problem open source? I haven't see these kinds of widespread problems coming from Java dependencies (25 years old) or Perl (maybe 30 years old)? Okay, maybe people aren't using Perl like they used to but Java is still a thing.
Re:Software is breaking down at a systemic level by codebje on Monday November 16, 2026 @03:43PM (#50522981)
I don’t doubt you would find a trove of issues in CPAN if you went looking. It’s not an interesting target, though, because it’s all but dead.

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.

Re:Software is breaking down at a systemic level by cmiles74 on Monday November 16, 2026 @04:41PM (#50523707)
I agree that CPAN is not as active as it once was. Maven is hardly dead, it's pretty active (as is Java the language). NPM is very busy but they also have a very real bot problem.
Re:Software is breaking down at a systemic level by codebje on Monday November 16, 2026 @08:14PM (#50526113)
Apologies, I didn't mean to imply Maven was dead, though I can see how it comes through that way. I meant to imply Java is less popular than other modern languages, and is a bit less interesting as a target as a result. Not unpopular, not dead.
Re:Software is breaking down at a systemic level by foopod on Monday November 16, 2026 @02:57PM (#50522277)
Yeah, I also question if this has anything to do with open source. Open source solutions have been around for decades, heck React has been open source for 13 years.

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.

Re:Software is breaking down at a systemic level by glassresearch on Monday November 16, 2026 @03:45PM (#50523002)
I have seen mostly engineers complain that management wouldn't stop paying for the new whizz-bang thingy.
Re:Software is breaking down at a systemic level by TZubiri on Monday November 16, 2026 @05:18PM (#50524209)
A decade ago there was a huge culture around having 100% uptime, nowadays it seems that not only is lower uptime acceptable, but services need to have some downtime and break when they are not profitable. Filtering out the undesirable users and upgrading them to plans with better economics is a new requirement in this age that wasn't present before during the growth stage and freemium VC backed startups