4 ms·
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 nod
by recursive 2y ago
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".
- cluckindan 2y ago”Usually”? Do you have some statistics on that, or do you just feel that way?
- recursive 2y agoJust feel that way. That's my anecdotal observation. YMMV.
- wswope 2y ago[Misread, mb - ty @Jarwain]
- Jarwain 2y agoYou may have mixed up who the commenter was replying to. They were specifically questioning "usually seen as an asset not a liability" bit
- bolognafairy 2y agoThat’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.
- Fauntleroy 2y agoThis 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.
- girvo 2y ago> 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...