Hacker News Reader

Comment by recursive | Hacker News Reader

In node projects, having more dependencies is usually seen as an asset, not a liability.

Other than that, I don't think there's a difference. When I write node projects, I tend to minimize dependencies, but I've seen PR comments saying "you know you could just get a package to do that".

View on HN

> In node projects, having more dependencies is usually seen as an asset, not a liability

Not in anywhere I've worked for the past ~decade...

Replies seem to be indicating my experience is the outlier. That's reassuring to me.

It was definitely the case prior, though, so you're not completely off base :)

This is an extremely weird thing to say. I don't know a single node dev who wants more dependencies. Anyone with a modicum of experience in the space knows the cost of bringing in more external code.

”Usually”?

Do you have some statistics on that, or do you just feel that way?

Just feel that way. That's my anecdotal observation. YMMV.

[Misread, mb - ty @Jarwain]

You may have mixed up who the commenter was replying to. They were specifically questioning "usually seen as an asset not a liability" bit

That’s really all there is in the comment. They’re unambiguously conflating “number of dependencies are higher” with some sort of statement about the value system of people that work with a certain language. It’s silly language tribalism.

Reply on news.ycombinator.com