Sorry Python but it is what it is.
this post was submitted on 13 Oct 2023
307 points (81.8% liked)
Programmer Humor
32503 readers
456 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
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I don't know what cargo is, but npm is the second worst package manager I've ever used after nuget.
cargo is the package manager for the Rust language
I've never had an issue with nuget, at least since dotnet core. My experience has it far ahead of npm and pip
I'll second this. I would argue that .Net Core's package/dependency management in general is way better than Python or JavaScript. Typically it just works and when it doesn't it's not too difficult to fix.
It's also much faster to install packages than npm or pip since it uses a local package cache and each package generally only has a few DLL files inside.
cargo is rust
what's wrong with nuget? I have to say I like the "I want latest" "no, all your dependencies are pinned you want to update latest you gotta decide to do it" workflow. I can think of some bad problems when you try to do fancy things with it but the basic case of "I just want to fetch my program's dependencies" it's fine.
I'm guessing they only used it 10 years ago when it was very rough around the edges. It didn't integrate well with the old .NET Framework because it conflicted with how web.config managed dependencies and poor integration with VS. It was quite bad back then.. but so was .NET Framework in general. Then they rebuilt from the ground up with dotnet core and it's been rock solid since
Or they just hate Microsoft, which is a common motif to shit on anything Microsoft does regardless of the actual product.
Imho the VS integration has always been good, it's the web config that's always been a trash fire, and that's not new.
The project I'm on right now originally had the nuget.exe saved in source because they had to manually run it through build scripts, it wasn't built in to VS until VS2012