- cross-posted to:
- hackernews@lemmy.bestiver.se
- cross-posted to:
- hackernews@lemmy.bestiver.se
I think in this text, details like the timeline are simplified a bit too much. But I agree with the general tendency described.
There was never a time where software was perfect, but the accelerating cadence of serious, widespread incidents with real-world effects seems real.


Rust (that is, cargo and crates.io) does in principle the same, and Java (via Maven) as well. Their quality is arguably better, but a lot of modern software has hundreds of dependencies.
I am wondering whether the SBOM philosophy is merely a box-ticking exercise. It does not buy you much when you know you have a buggy 15 years old TCP stack in your industrial control, but you can’t upgrade it because there is no storage left on your device. And the same holds for Cisco routers. Constantly upgrading works,in my experience, only with completely open systems like Linux, on open hardware.
Which by the way also leads to an interesting state of matter once you reach the point where every dependency problem you fix causes on average more than one new problem elsewhere. The reason is that if dependencies are not strictly backwards-compatible, that’s a breaking change – and with large depedency graphs, breaking changes tend to cause more breaking changes. You get kind of a nuclear chain reaction.
Which is the reason you lock down the dependencies and maybe you build a in-house server to host them (be NPM, composer of whatever) so everyone fetch a certified version and it is the same for everyone on every project, with an upgrade that need to follow a strict process.