Language Package Managers
Discussions center on the proliferation of separate package managers for each programming language, their drawbacks compared to OS package managers, and debates over their necessity and effectiveness.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Why do we need a separate package manager for every programming language and every extensible library/app?
Why do people keep writing domain-specific package managers?
why do we have to have soooo many package managers? makes me cry inside a bit.
This doesn't introduce a new package manager to the world
Do we really need a separate package manager for every programming language? They all seem to have their own, which creates pressure to "re-implement ALL the things" every time a new language becomes popular. In 2013, why can I still not declare that my C library depends on a Perl module, except on individual Linux distributions?
How do people live without package managers? It's complete chaos!
Just curious. Why do you have doubts about about the package manager? There are so many languages that have a package ecosystem, so by now you'd think its easy to find out what works and what does not.
Package managers are a language specific thing.
Have other languages with package managers a similar problem? (Ruby, Lua, Go, Python, PHP, etc)
Iād consider the issue to be the opposite. Why does every programming language now have a package manager and all of the infrastructure around package management rather than rely on the OS package manager? As a user I have to deal with apt, ports, pkg, opkg, ipkg, yum, flatpak, snap, docker, cpan, ctan, gems, pip, go modules, cargo, npm, swift packages, etc., etc., which all have different opinions of how and where to package files.On packaged operating systems (Debian, FreeBSD) - you have th