> Why is that a problem? If you have a large library, surely it's better to properly break it up into separate files?! That's at best good for developing the l

> Why is that a problem? If you have a large library, surely it's better to properly break it up into separate files?! That's at best good for developing the library (even that is debatable though), but definitely not when just using the source-distribution of the library in a project. > What's the reason C resists so much using a package manager... One important problem is that there are so many package managers and build systems for C and C++ projects. So the choice for a library author is either to support all package managers and build systems (not really a realistic option), or none specifically (much better but requires that the library source distribution is designed for simple integration into projects without esoteric build requirements). Requiring a specific package manager and build system is hostile to users preferring other tools. The problem doesn't lie with C or C++ users, but with the respective language committees saying "dependency management and build system standardization isn't our problem".