Sorry Python but it is what it is.

you are viewing a single comment's thread
view the rest of the comments
[–] 28 points 2 years ago* (4 children)

I don't know what cargo is, but npm is the second worst package manager I've ever used after nuget.

  • source
  • hideshow 8 child comments
  • [–] 10 points 2 years ago (1 child)

    I've never had an issue with nuget, at least since dotnet core. My experience has it far ahead of npm and pip

  • source
  • parent
  • hideshow 2 child comments
  • [–] 8 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 2 years ago* (1 child)

    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.

  • source
  • parent
  • hideshow 2 child comments