3 ms·
Small packages are fine, if the maintainers keep them up to date! You can't publish packages and never touch them again. This leads to situations like the one w
by wereHamster 7y ago
Small packages are fine, if the maintainers keep them up to date! You can't publish packages and never touch them again. This leads to situations like the one with merge-deep that I recently discovered:
http://npm.anvaka.com/#/view/2d/merge-deep http://npm.anvaka.com/#/view/2d/merge-deep
All but one of those dependencies are from the same maintainer. Yet I see two major versions of kind-of, for-in, and lazy-cache. What's the point of creating reusable functions if you're not going to reuse them?
This is a huge waste. First on the filesystem, no wonder our node_modules folders are hundreds of megabytes big. Second it wastes bytes in memory and in CPU caches since they don't share byte code and each function has to be parsed, compiled, optimised separately.
I seem to be in the minority thinking this situation is insane…
- unlinked_dll 7y agoIt's insanity all the way down to the copper on the board frankly. People only care about making things more sane when you can prove there's a dollar to be made or saved by doing so. Like we all know nodjs is slow(er than other things). The question is not how to make it faster by doing things like keeping dependencies up to date but how much there is to gain by doing so. I suspect very little.