3 ms·

I'm not trying to be that guy, but NuGet.org is littered with bad packages, and it's hard to see, at a glance, what packages are commercial, trials, or open sou

I'm not trying to be that guy, but NuGet.org is littered with bad packages, and it's hard to see, at a glance, what packages are commercial, trials, or open source. Some packages are not even .NET packages. The default search scoring could also benefit from some work as old, unmaintained, packages often show up on the first page. I wish there was a way to filter by license, open-source, and/or source-code-package. I've been a .net guy ever since C# was called COOL and I even went to Redmond back in the days as part of the early adopter program. I'm worried about the adoption and I think it's mainly because of the perceived low quality when it comes to browsing NuGet.org Compared to npmjs.org, NuGet.org could be soooo much better.

octopoc 6y ago
> 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.