Also, from the stories I've seen, the big issue with old systems that still have COBOL parts etc isn't so much the COBOL itself as all the domain-specific, prop

Also, from the stories I've seen, the big issue with old systems that still have COBOL parts etc isn't so much the COBOL itself as all the domain-specific, proprietary, custom developed integration solutions that have to be reverse-engineered for someone to replace them.