@coder @MaddieM4 @elebertus The thing is, if you know your dependencies you can get from there to whatever containerization you want pretty easily. But the reverse is very, very not true.

I mean, Docker was born because somebody told an ops person "well it works on my machine" and the ops person said "well we'll ship your machine then" and from the stories I've heard it took _years_ to stabilize and secure AWS after starting with that as a foundation.

@mhoye

> know deps -> containerization; reverse is space aids

Exactly. Which to your original point of `make`-n-bake, who cares if it is maven, or ninja, or whatever build system, thats all good. When you start having deps on things like gcc and openssl thats where containers start being a lot more friendly.

Which I think maybe to the security point too is your systems running the containers may be patched and modern but that doesn't prevent someone from copy-pasting some reckless pin on a not safe version of openssl for example.

Which.. there is also an entire ecosystem around enforcing container standards and scanning (as I'm sure you're aware).

I still don't really get the hate for containers outside of my example though.

@coder @MaddieM4