> NuGet.org is littered with bad packages, and it's hard to see, at a glance, what packages are commercial, trials, or open source True, but on the other hand,

> NuGet.org is littered with bad packages, and it's hard to see, at a glance, what packages are commercial, trials, or open source True, but on the other hand, there are some areas where NuGet is better than npm. For example: - Backwards compatibility is more common in the .NET world. - .NET libraries tend to reinvent small wheels rather than adding a new dependency. I feel like npm has gone too far with the "don't reinvent the wheel" concept.