2 ms·
If that's the case, that is rather excessive. I hope there's at least a movement going on to shift towards using utility modules that combine a few tens of the
by kbenson 11y ago
If that's the case, that is rather excessive. I hope there's at least a movement going on to shift towards using utility modules that combine a few tens of these one-liners into a cohesive namespace/class/object where complementary. Keeping track of many, many very small modules does indeed impose a cost, which it looks like some NPM users have gotten around by doing the absolute minimum to keep track. This is the result.
- brudgers 11y agoThere are modules that combine modules. Alas due to the beauty and power of combinatorics, there will inevitably be more compound modules than atomic ones. If there are not already.
- kbenson 11y agoYeah, I meant combine less in the "concatenate into one large new module automatically" and more "someone as put out what is rapidly becoming the de-facto standard for all OS high level actions in a comprehensive single module." I don't see automatic combination of lots of small modules actually making this situation better in any way. Quite the opposite, actually...