There's certainly a strong Old School mentality in the C/C++ that says that you throw code into a repository somewhere with build instructions, and if other people want to use it in their project it's on them to package it for their system and worry about coordinating, building, and installing other dependencies. There is no "language community" so much as a Debian community and an Arch community and an OS X community and a Windows community and each and every platform should attempt to "Package the World" and solve this problem in its own way. The author cares not.

Count me among the New School that feels that if you want to share your code, you package it yourself, declare its dependencies in a standard way and throw it into a central, community organized place and the whole community immediately benefits from it using a standard tool that pulls down your package and its dependencies on demand, regardless of platform.

Having come to the New School from the Old School, it moves so much faster, and there is infinitely less friction when it comes to sharing code. To point at an obvious example, Common Lisp post-Quicklisp is an infinitely more pleasant and vibrant community to work in than it ever was previously.

Agree to disagree, I guess.