It’s exacerbated by “oh this library is updated for no reason than its version is newer so we need to force that bleeding edge on any ecosystem we’re in” thinking.
We’ve absolutely lost the careful, measured long-term release and maintenance cadence that we built the Internet on.
Compare Systemd.
3abas@lemmy.world 2 days ago
The worst dependency hell is when a library has a strict version dependency, and another library uses that same dependency. When the second library updates their minimum version of the dependency to one that is higher than the exact version needed for the first, THAT’S dependency hell.
phlegmy@sh.itjust.works 2 days ago
This wouldn’t be a problem if libraries didn’t frequently make breaking changes to their api.
“Move fast and break things” is for startups with no userbase, not libraries with millions of users.
clif@lemmy.world 2 days ago
There are times when things need to be broken. But I also definitely understand your angle.