Comment Re:Still trying to wrap my head... (Score 1) 51
This isn't the '90s. Compared to hardware resources today, yes, an operating system is a thin runtime environment. Most of the resources are shared and usually they are abundant.
Using containers simply means you get yet another abstraction layer, that needs to be managed in yet another way, that will eventually evolve into being exactly the same thing as that operating system you tried to get away from.
Frankly, I'd rather be managing 1000 guests with 1000 apps, because once I have enough automation to spawn and manage guests on demand I don't want them being unique snowflakes and get the accompanying maintenance nightmare because they each host so much that they create infrastructure dependencies.
For most small to medium scale operations the main cost will be the personell needed for management. If you're only running a lot of things you can deploy and support on something like containers or even better openshift, that might be the better option. But if you're running a lot of things that you need to dink around with, even to a minor extent, and will run into support issues with, then you're just creating a resource drain on the one resource that's actually expensive: your admins time.