You're right.

Although it's a bad point without any concrete examples. Without that, it just seems like a baseless emotional reaction to not liking something new. I might even be inclined to agree if there was a bit more detail given.

Containers are a solution looking for a problem, used more for organizational reasons than technical.

Disclaimer: Infra/DevOps engineer previously, 20 years total in tech

I hear things like this a lot but I never hear how you could accomplish the same things as Kubernetes (or any other orchestrator) without containers. Even if there were good solutions available for this, and the only advantage of containers was an organizational advantage rather than a technical one, I think that would still be a win.

The same way we orchestrated before containers: VMs, config management, and APIs at the control plane

There is a certain level of saltiness that is well deserved, and I'm not sure that the GP came close to strong enough. We're swirling around in circles, rediscovering the same thing every five years, leaving a blasted wasteland of half-baked abandoned technologies behind, endlessly chasing the shiny - and overwhelmingly, it's the extreme ignorance and illiteracy of the profession that is to blame.

“””it's the extreme ignorance and illiteracy of the profession that is to blame.”””

I’m imagining a thought experiment... the requirements to understand and operate in this industry... for example this article that was posted . Imagine giving it out at a family reunion and asking each relative if it makes any sense at all. Even the ones who are developers might only get a small gist of it if they program java code. For humans to digest decades of information written by 1000s of other humans in terse code ... it’s a daunting task which is married to the side effect of accidentally repeating past mistakes. Maybe if we had an Oracle to help us... oh wait that’s a terrible joke