Hacker News Reader

I have different priorities than you. In terms of IDE quality, debugger quality, flexibility (ability to use actual threads if you want them!), performance... in my opinion .NET Core is already so far ahead of Node.JS it's embarrassing for them.

The only thing I might stack in Node.JS' favor is their NPM package manager. Maybe. Possibly.

View on HN

Are you seriously saying that NuGet/paket are worse than a flawed package manager that even managed to cause a JavaScript global outage when a padding package was retired? What are your problems with NuGet and paket?

Re-read my post.

Nuget dependency management is a nightmare for my team. Mostly because there's usually only one package for a given problem, and you're always at their mercy. I suppose it's a community issue, because npm packages I seem to find few complications. Also, I always find plenty of documentation/tutorials/friendly community to help with the package, and never anyone expecting money for a out-of-date pdf generator that works with tooth-picks and bubble gum holding it together (for example). The manager in VS has gotten better, but it's still far more cumbersome than a cli.

Reply on news.ycombinator.com