Programming

28009 readers

421 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

[–] trem@lemmy.blahaj.zone 5 points 23 hours ago

You want some way to define package versions in your repository, so that you can check out an earlier commit or a different branch and still have a working build. Because you do often need to adjust the code in your repo when dependencies get updated.

And going upwards from there, I think that languages are just a point where it's quite natural for this to be solved, since the language creators care to build up an ecosystem and it does help when you can make language-specific assumptions.

I do think, it's possible to create a package manager that spans across programming languages, like Nix is starting to be viable for.
But you need that to be ready when a new programming language is starting to take off. For all the languages you listed, that choice was made many years ago and you can't easily reverse it.