Programming

28027 readers

433 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 3 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

UlrikHD@programming.dev

bugsmith@programming.dev

Spyro@programming.dev

Why do so many programming languages have their own package manager? (sh.itjust.works)

submitted 2 days ago by DeltaWingDragon@sh.itjust.works to c/programming@programming.dev

41 comments fedilink hide all child comments

cross-posted from: https://sh.itjust.works/post/64685863

Lots of programming languages have their own package manager, separate from the distribution or OS package manager.

Going loosely from the TIOBE index:

Python has Pip

C# has NuGet

Javascript has npm for Node.js

Visual Basic also uses NuGet

R has a repository of packages that can be installed by running install.packages("something") in R

Rust has Cargo/Crates

Go has the go get command

Swift has its own package manager swift package

Ruby has RubyGems

Java has Maven and Gradle (not sure if they are full package managers, or build automation tools with dependency resolution)

PHP has Composer for managing libraries and dependencies

C and C++ are the only exceptions I can think of, off the top of my head; libraries are managed by, and coupled to, the operating system

you are viewing a single comment's thread
view the rest of the comments

[–] one_old_coder@piefed.social 6 points 2 days ago* (last edited 2 days ago) (2 children)

Each project would have to reinvent the wheel and make packages for the 10 most popular Linux distributions (every one of them being different, DEB, RPM, Arch, etc.), Windows 10, Windows 11, macOS latest version, macOS previous version, and macOS future version.

Also you would need 10 virtual machines to test on Linux, 2 virtual machines for Windows, and 3 Apple computers. That would be so easy.

[–] kuberoot@discuss.tchncs.de 1 points 15 hours ago

Yeah, it's so annoying how every crossplatform project is having to do that, it's such a burden on all those indie developers all managing so much hardware and automation to support those platforms. /s

I think I've seen the same argument against Linux package managers in general, and it's bullshit in the way that it's not on the projects to package for each distro, it's on the project to provide a functioning build system, or at least binaries, and from there it's on the distribution maintainers to figure out packaging.

But also, in cases where packaging is more complex than just one dependency system for a whole language, it would be beneficial to have one unified system - if all languages are packaged in a unified way for specific system package managers, then you only need to develop a system for them once across all languages, and then you might have one system you need to plug your project into, and from there it could be automatically packaged into all those systems.

[–] TrickDacy@lemmy.world 2 points 1 day ago

Haha sure I guess. I think before package managers people used a hodge podge of manual systems to manage dependencies and it sucked. Your way sounds even worse tbh