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 rumor persists for so long. I’ve been in tech for now twenty years, and juniors say this all the time. Also, I’m hired to replace archaic code with modern equivalents, so my perspective is one from the other side.
A few key things I discovered:
Finally, those archaic systems get forced into retirement. Yes, there are still integrated systems like ATM and missiles or whatever that use these languages.
But that’s so extremely rare that they’re still being maintained. Because companies will allocate a budget to have some dipshit programmer like me come in, rewrite the functionality in whatever language (the last one I did was a interface from a PoS system to a web application, which I did in PHP), and then throw away the old code because ain’t nobody want to fix that.