Packaging
Ah, yes, I remember the good old days of running "./configure; make; make install" and just having it turn out all right with no unresolved dependencies whatsoever, especially not issues with the developer having statically linked to one particular version of a library in another package and thus having the software fail to build. Nope, that certainly never happened. Likewise, I have never struggled with RPMs that fail to install because they depend on a particular micro-version of an obscure package and adamantly refuse to accept that version 1.3.11511516-33 is just as valid as 1.3.11511516-32. Not saying that containers solve all those problems, but they do put more power in the developers' or package-builders hands to ensure that dependencies are resolved before deployment.
Biting the hand that feeds IT
