Many have issues with the idea that one should create libraries containing one function only! You've touched yourself upon the why: having hundreds of dependenc

Many have issues with the idea that one should create libraries containing one function only! You've touched yourself upon the why: having hundreds of dependencies adds both technical and cognitive overhead. Indeed. Moreover, it's a sign of a weak or incomplete standard library. Early Java had this problem as well. However, since distribution consisted of passing around JAR files, most utility code was bundled in larger libraries (e.g., see commons-.*).