While i sympathize, the world does rely on high quality 30+ year old software. I think it's time, as an industry, to stop seeing software as disposable and start designing for longevity.
Except maintenance of software looks more like continuous architectural review and operation of an electrical grid. Calling it maintenance is a little narrow.
But we can't seem to move past archaic UNIX architecture.
_but_ that would require a stable ABI. Which is specifically called out as not desired here https://www.kernel.org/doc/html/next/process/stable-api-nons...
There are valid concerns, but the analysis doesn't lay out the issues with the current design either making it a one sided review.