This seems to be the thing: an ecosystem has a bad system (npm, pip, gem, deb stuff), someone decides the system is bad or has bad documentation, and writes som

This seems to be the thing: an ecosystem has a bad system (npm, pip, gem, deb stuff), someone decides the system is bad or has bad documentation, and writes some new tool (yarn, pipenv, debcraft), and that becomes the new standard for a while. Then 4-6 years later someone does the same thing again. When you return to the ecosystem after a while you find that there are three layers of outdated “new hotness” CADT you have to sift through. Only Go did this right by getting the first-party tooling right from the outset (and then upgrading it, again first party, with modules). Nix seems to have come close but now there are Nix flakes which seem to be the same pattern. It’s called “deb”. Debian should fix this. The fact that they’re spending their time removing version notices in xscreensaver and not fixing the basic tools and formats used is a mistake.