Hacker News Reader

Comment by Pacabel | Hacker News Reader

I don't see why codereflection needs to spell it out. The problems with npm, and JavaScript in general, are quite apparent to anyone who has used them. And if you haven't used them, a quick search engine search will turn up this information many times over.

It'd make sense to ask for such clarification if the information truly wasn't available elsewhere, and accessible with a quick search. But that's obviously not the case.

It's pointless to rehash this obvious stuff over and over and over and over again.

View on HN

It'd be good if there were a canonical "Why npm sucks" article, like the "fractal of bad design" one for PHP.

This one seems like a fairly reasonable candidate: http://www.jongleberry.com/why-i-hate-npm.html (though the "nested dependencies" bit needs much more swearing, and I disagree with the last paragraph suggesting things in Ruby and Python land are just as bad).

In the last paragraph there, is he saying that Golang is 'bad' because it doesn't have a package manager? Does it need one? I always assumed 'go get' was enough.

Honestly curious here.

So you want a list of out of date and idiotic problems interspersed with a few actual issues?

I hadn't seen that post before. I agree with most of it. Nested dependencies is my main complaint about NPM.

It is certainly isn't obvious to me. NPM is the best package manager I have used for a specific language. I do think there are things that can be improved, like everything else, but overall I think it is pretty good. And the vast majority of complaints I have seen are just nitpicks. So yes I would be very curious to know what you think is so obviously broken with it.

Look at this link http://www.jongleberry.com/why-i-hate-npm.html I agree with a lot of the points there

While I don't hate npm, there are better examples of how to do package management. For example, Nuget gets a lot of things right with no nested dependencies.

Reply on news.ycombinator.com