(And I agree with the GP. I'm fairly cynical about most developers' security stance and threat model. Source: my own usage patterns.)
https://www.docker.com/blog/2025-docker-state-of-app-dev/
I welcome your apology.
No accusations were made.
And also clarify that it's all lie. He just want to tell the anonymous crowd "look, I'm better than you".
"Just 30% of developers say they use containers in any part of their workflow." https://www.docker.com/blog/2025-docker-state-of-app-dev/
So, yea. Large companies, yes, for sure. But that's not 100% - is it.
If I hand them an image for a Dev Container, sure, they might use it, but it becomes "a thing we need to do, to compile our code in our IDE" not a tool they would use for isolation*.
*) OP seemed to imply that containerization would be nice for safety and security compared to bare metal, but containers were never built for isolation in the first place, mind you. They are namespaces and chicken-coop-like-jails at best.
There was some user chroot thing early on that required me to make a library to intercept the setuid calls to pretend the garbage root-only build system was running as root on everyone else's lowly user account.
And that's not even including the myriad of distroboxes I need to do anything at all on my gaming pc.