4 ms·
Actually, all software packaging problems today stem from software development practices. Software developers don't make languages, build tools, or dynamic libr
by 0xbadcafebee 6y ago
Actually, all software packaging problems today stem from software development practices. Software developers don't make languages, build tools, or dynamic libraries, that support compatibility with different versions of dependencies in a way that is widely compatible.
Right now, as a dev, you have to make your code work with one version of a dependency, and hope that the way you did it is widely compatible. But why is this the only way to do it? Because nobody has improved on this model yet.
It's actually very simple to fix. Glibc actually already supports loading a specific version of a specific dependency from a specific shared library version for each and every function. So you can build a single app that works with conflicting library versions. Just write your function against one version, and if there's a breaking change, write another version of the function. Then load the right one at run time. Now you support multiple versions of dependencies.
Once that becomes a common convention, package managers no longer need to restrict systems to only one version of a dependency, and we no longer have to deal with "bundling". Is this more work for the developer? Yes. But it also solves all the problems that affect developers, packagers, and end users, by allowing for a maximum amount of compatibility.
The alternative of course is for devs to just stop writing breaking interfaces, and to handle versions in those interfaces so breaking changes can be handled gracefully.
- pacifika 6y agoHow is keeping compatibility with a historic set of libraries simple?
- 0xbadcafebee 6y agoI guess it's not... I was thinking "simple" in the sense that we have a solution, and we just need to implement it.