I think you are jumping to conclusions about me. This is not about me.
You are right that it is not just about process. Process is part of it. The largest issue, IME, is knowledge: do people know about VMs? Containers? ATDD? DevOps? etc. - at all levels, from the developers through the various managers who set the rules (and therefore can change the rules).
One thing that I have found is that if you give developers Windows machines, they learn that - they don't learn about Linux. That's fine if the org deploys on Windows, but if it deploys on Linux, it is nice if the devs know about Linux; and if you want them to know about Linux, the best way to achieve that is to have them live in Linux most of the time.
There are always exceptions: people who will learn all of the envs. That's why I don't believe in forcing people to use one env over another. Most of my work is in large organizations where one has to think about the range of skills and personalities.
PS - Don't assume that because I am an Agile transformation coach that I am not technical - I am (I code).
It is also true that for centuries people did not go to the moon. And then, in 1969, they did.
History is not always a guide. In fact, due to technology, history never repeats - only human behavior patterns repeat.
What is different how is that it is very likely that AI will attain human level thinking ability within the next decade. And that _is_ a game changer.
Make sure your code does nothing gracefully.