3 ms·
It's a lot easier to add a dependency or a sub-dependency, so people split libraries further than they'd do in C++ and are less likely to write code/include it
by detaro 8y ago
It's a lot easier to add a dependency or a sub-dependency, so people split libraries further than they'd do in C++ and are less likely to write code/include it in the library directly instead of just importing another dependency for it. A "dependency" can be just one or two functions, something you'd never make a library for in C++. And of course if it is common for dependencies to have dependencies, than those dependencies also are gonna have dependencies and ...
E.g. imagine C++'s Boost libraries: That's I think ~150 libraries with dependencies among each other? Now imagine there was no need to publish them together, so each of them is an individual library that could pick any random dependency, not just primarily from inside the set of 150. And split some of them up in 4-10 pieces doing parts of their task. And external projects of course also then depend only one some subset of those parts.
A relative lack of a standard library maybe seeded the principle that people go looking for libraries for small things.