4 ms·

Here's the other side of the coin, as someone who's worked primarily with npm (JS), composer (PHP), had a taste of cargo (rust) and of course yum, apt-get, etc.

Here's the other side of the coin, as someone who's worked primarily with npm (JS), composer (PHP), had a taste of cargo (rust) and of course yum, apt-get, etc.: packages are awesome. npm is weird and hellish because people write single-function packages, but that isn't the case in other ecosystems. NuGet provides an easy and familiar way for me to get into it, as opposed to having to absorb the entire ecosystem at once. I agree though, that the challenge is different in a compiled language (from JS/PHP), and when dependencies get specific you might be out of luck (when .NET Core was announced I had a hard time following Microsoft's own tutorial because minor revision was different between two key packages)

douche 10y ago
Nuget does get a little fun when you are dealing with a solution with multiple library projects that feed into a final executable. So far, I've either had to upgrade all versions of a Nuget package across projects, or spend a lot of time messing around with app/web.config assembly redirects. At least the granularity of Nuget packages is not at npm-level fineness, although it does sort of feel like it is trending in that direction.
- smoothdeveloper 10y ago
  Try paket, will save you a lot of headaches with the redirect stuff
vamsipk 10y ago
_packages are awesome. npm is weird and hellish because people write single-function packages, but that isn't the case in other ecosystems_ I have no knowledge of how NuGet works but is there anything in NuGet that is stopping the developers from writing/using single line packages?
- xorxornop 10y ago
  Technically, no, but the proliferation of those in the likes of the npm ecosystem is almost entirely due to the shittiness of the JS standard library (such as it is...) . NET, however, has an excellent stdlib, so in practice you simply do not get packages like this.

douche 10y ago

Nuget does get a little fun when you are dealing with a solution with multiple library projects that feed into a final executable. So far, I've either had to upgrade all versions of a Nuget package across projects, or spend a lot of time messing around with app/web.config assembly redirects. At least the granularity of Nuget packages is not at npm-level fineness, although it does sort of feel like it is trending in that direction.

smoothdeveloper 10y ago
Try paket, will save you a lot of headaches with the redirect stuff

vamsipk 10y ago

_packages are awesome. npm is weird and hellish because people write single-function packages, but that isn't the case in other ecosystems_ I have no knowledge of how NuGet works but is there anything in NuGet that is stopping the developers from writing/using single line packages?

xorxornop 10y ago
Technically, no, but the proliferation of those in the likes of the npm ecosystem is almost entirely due to the shittiness of the JS standard library (such as it is...) . NET, however, has an excellent stdlib, so in practice you simply do not get packages like this.