AI is destined to destroy software industry, but not itself.
Software does not decay by itself (it's literally the whole point of using digital media over analog). "Bit rot" is an illusion, a fictitious force like centrifugal force in Newtonian dynamics, representing changes that happen not to a program, but to everything else around it. The current degree of churn in webshit ecosystem (whose anti-patterns are increasingly seeping in and infecting other software ecosystems) is not a natural state of things.
I hear you about damning shitty code which the web industry as a whole is quite responsible for, but I don't see how them dying outright is better.
Your original point was that libraries do not need companies behind them. From what you have written here a reason for that is that (web) libraries mostly create churn by introducing constant changes. What I think you follow from that, is that those libraries aren't necessary and that "freezing" everything would not do any harm to the state of web development but would do good by decreasing churn of constantly updating to the newest state.
What I struggle to understand is (1) how does AI fit into this? And (2) Why do you think there is so much development happening in that space creating all the churn you mention? At this point in time all of this development is still mostly created by humans which are likely paid for what they do. Who pays them and why?
But after just months of being unmaintained, even the best libraries start to rot away due to bugs and vulnerabilities going unfixed. Users, AI included, will start applying workarounds and mitigations, and the rot spreads to the applications (or libraries) they maintain.
Unmaintained software is entropy, and entropy is infectious. Eventually, entire ecosystems will succumb to it, even if some life forms continue living in the hazardous wasteland.
Bit rot isn’t some mystical decay, it’s dependency drift: APIs change, platforms evolve, security assumptions expire, build chains break. Software survives because people continuously adapt it to a moving substrate.
Reducing churn is good. Pretending maintenance disappears is fantasy. Software doesn’t decay in isolation, it decays relative to everything it depends on. And it sounds like you don’t know anything about Newtonian dynamics either.
Given that countries/cities can go into this state for a very long time without resolution, I am not quite optimistic.
1. Plant new trees,
2. Eat fruit from trees, get used to delicious fruit,
3. Planting trees hard, easier to wring out more juice from existing fruit,
4. Forget how to maintain trees, trees die, go to 1.
We are entering stage 3.
There are people who will use AI (out of their own pocket for trivial costs) to build a library and maintain it simply out of the passion, ego, and perhaps some technical clout.
That's the same with OSS libraries in-general. Some are maintained at-cost, others are run like a business where the founders try to break even.
AI eats up users caring about $company which makes library, library degrades because nobody is paying, $company goes insolvent, library goes unmaintained and eventually defunct, AI still tries to use it.
Vibe coding with libraries is a fad that is destined to die.
Vibe coding your own libraries will result in million line codebases nobody understands.
Nothing about either is sustainable, it’s all optics and optics will come crashing down eventually.