COBOL turned 66 this year and is still in use today. Major retail and commercial banks continue to run core account processing, ATM networks, credit card clearing, and batch end-of-day settlement. On top of that, many payment networks, stock exchanges, and clearinghouses rely on COBOL for high‑volume, high‑reliability batch and online transaction processing on mainframes.
Which reminds me, mainframes are still alive and well too. Banking, insurance, governments, inventory management – all the same places you’ll find COBOL, you’ll find mainframes as well.
None of that is as sexy as the latest AI program or the newest cloud-native computing release, but old dogs with their old tricks still have useful work to perform.
This is one of the reasons COBOL programmers get paid extremely well. Nobody is learning it anymore and these people are critical if an issue occurs.
dan@upvote.au 1 day ago
Rewriting existing systems is one of the riskiest things a company can do. Those old COBOL codebases likely contain 50 years of bug fixes for every possible edge case. It’d take a long time to rewrite everything and ensure feature parity, and there’s usually not a significant business reason to rewrite it (after all, a successful end result is just that the system behaves exactly the same as the old one).