4 ms·
If you consider 27 TB a good thing, you to some degree invite code bloat. Libraries should be small and carefully designed.
by avmich 4y ago
If you consider 27 TB a good thing, you to some degree invite code bloat. Libraries should be small and carefully designed.
- invalidname 4y agoI would say they should be the "right size". 27TB isn't one library. It's the amount of libraries there are. In the NPM world there are too many small libraries that create a dependency graph that's impossible to parse mentally. No one knows your true dependencies and that created many problems. In Maven libraries are sometimes too big. That's true. But most of them are closer to the size that gives a library a bit of "meat". Obviously YMMV.
- kaba0 4y ago27 TB is about the vast amount of choice in the ecosystem. Try to delete the node_modules folder vs the .m2 one on windows — only one of these chokes out a high-end laptop. In my experience Java dependency trees are not as absurdly deep as JS’s. Sure, frameworks do add quite a few nodes to the tree, but libs don’t have as many transitive deps as they do in JS, perhaps due to the better standard lib.