I learned COBOL in early 1970s while in high school and later even had opportunity to have dinner with inventory Grace Hopper twice at our ASM and DPMA meetings in Roanoke decades ago. I wrote last COBOL program back in 2013 for a former client. While other programming languages are more popular today, COBOL continues to survive in many organizations with IBM mainframes.
COBOL has been around since Eisenhower sat in the Oval Office. At one time, it was estimated that 80% of all business applications were written in COBOL — a total that represented more than 2 billion lines of code. That was nearly 20 years ago. Does COBOL still matter to the world of enterprise IT today? Many people seem to think so.
And, why do we care? In part, it’s because there are lots and lots of applications written in COBOL that remain part of the enterprise IT landscape. And, like many other things with historical foundations, COBOL has a whiff of the “retro-cool” about it: You can even get COBOL development environments that run on Raspberry Pi. There are a number of options for someone who wants to use COBOL — the real question is why you might want to do so.
The first reason is employability. As noted, there are still plenty of companies running applications built on COBOL. And not all of those applications are archaic: Since 2002, COBOL has had an object-oriented framework. And as you’ll see, a number of the options we list have Java as an intermediate target — a strategy that has both plusses and minuses when it comes to performance and compatibility with other applications.
The next reason is readability. COBOL is known as a “verbose” language, especially when it’s compared to a very terse language like C++. From a debugging standpoint, COBOL can be like reading a novel. So let’s take a look at the modern options in COBOL. Let us know whether you’re using COBOL — and why. Surely the story will be as compelling as one written in Grace Hopper’s legacy language…