322
Package managers be like
(linux.community)
Sorry Python but it is what it is.
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 13 Oct 2023
322 points (81.3% liked)
Programmer Humor
32707 readers
288 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
cargo just works, it's great and everyone loves it.
npm has a lot of issues but in general does the job. When docs say do 'npm install X' you do it and it works.
pip is a mess. In my experience doing 'pip install X' will maybe install something but it will not work because some dependencies will be screwed up. Using it to distribute software is pointless.
I use pip extensively and have zero issues.
npm pulls in a million dependencies for even the simplest functionality.
Is that really the fault of the package manager or is it of the libraries you decide to use?
Fault of the libraries you decide to use, i.e. any and all node libraries
Well if that's the case, can't argue with that lol
Really the fault of js since its standard library is so lacking (leftpad, anyone?), but js wasn't built to do half the stuff it's being asked to do, anyway.
You’ve never had broken dependencies?
Nope. I know mixing pip with python packages installed through your systems package manager can be a problem but that’s why I containerize everything.
I separate everything in virtual environments myself, but in my opinion you shouldn't need to that to simply avoid breaking your system.
It probably works for your own local project. After using it for couple of days to install some 3rd party tool my conclusion is that it has no idea about dependencies. It just downloads some dependencies in some random versions and than it never works. Completely useless.
This is clearly a layer 8 issue lmao.