However, I have worked in some of those environments where programmers refused to change, admittedly due to their unwillingness to learn despite their customer wanting the change. Even at organizations with large risk-adverse datasets, there's a desire to change but an inability to execute. The VA for example, has struggled for decades to modernize their system despite sinking millions and millions of dollars into it.
>If it's running now, it'll most likely continue to run for the next 20 years of software and hardware updates.
This is fine if the system is expected to remain static. Problems often arise when hardware or software are expected to change and still run the same legacy code.
One of the selling points of IBM mainframes is the pretty flawless backwards compatibility. I wouldn't be surprised if you could run unmodified binaries compiled for the 360 model 20 on a z15.
Governments use to have extremely large databases of extremely critical data that has to be collected and processed in a secure, correct, and timely basis or the agency will be in breach of some law that governs it. It's not surprising they were early adopters of large computers.
Traditionally, everything that's not forbidden is implicitly permitted in private initiative. In government, it's usually the reverse: anything that's not explicitly allowed by law is forbidden. And sometimes a crime.
This selects for very risk-averse organizations. The environments where these COBOL programs run are also remarkably stable. If it's running now, it'll most likely continue to run for the next 20 years of software and hardware updates. A lot of systems still think they are reading and writing tapes.