COBOL remains the dominant language of mainframes. What can Go learn from its history to dominate the cloud?
COBOL dominates the mainframe
One of the most brilliant minds in all of computer science is Grace Murray Hopper. Every time we don’t have to write in binary to talk to computers, I recommend saying out loud: “Thank you, Rear Admiral Grace Murray Hopper.” Try it next time, for she is the one who invented the first compiler (the software that translates programming code to machine language).
Hopper was essential to the invention and adoption of high-level programming languages, including COBOL. She helped create the COmmon Business-Oriented Language (COBOL for short) in 1959. As Ritika Trikha put it on HackerRank:
“Grace Hopper, the mother of COBOL, helped champion the creation of this brand-new programming language that aimed to function across all business systems, saving an immense amount of time and money. Hopper was also the first to believe that programming languages should read just like English instead of computer jargon. Hence why COBOL’s syntax is so wordy. But it helped humanize the computing process for businesses during an era when computing was intensive and prevalent only in research facilities.”
In the early 1960s, mainframes were a wild new architecture for sharing powerful amounts of computation. And in the era of mainframe computing, COBOL dominated the landscape.
COBOL in today’s world
But what about today? With the decline of mainframes and the rise of newer and more innovative languages designed for the web and cloud, where does COBOL sit?
Fast forward to 2019, and COBOL has far from “trailed off.” As David Cassel wrote on The New Stack in 2017:
“About 95% of ATM swipes use COBOL code, Reuters reported in April, and the 58-year-old language even powers 80% of in-person transactions. In fact, Reuters calculates that there’s still 220 billion lines of COBOL code currently being used in production today, and that every day, COBOL systems handle $3 trillion in commerce.”
Given its continued significance in the business world, knowing COBOL can be a great career move. Top COBOL programmers can expect to make six figures due to the limited number of people who specialize in the language.
Go dominates in the cloud, for now
That story of COBOL’s early dominance rings a bell for me. If we survey the most influential projects of this cloud computing era, you’d be hard-pressed to miss Go sitting at the top of the pack. Kubernetes and much of its related technology—from Etcd to Prometheus—are written in Go. As RedMonk explored back in 2014:
In two of my previous jobs, my team (re)wrote infrastructure software in Go to be part of this monumental wave. Influential projects continue to live in the space that Go can fill, as Uday Hiwarale explained well in 2018:
“Things that make Go a great language [are] its simple concurrency model, its package-based code management, and its non-strict (type inference) typing system. Go does not support out-of-the box object-oriented programming experience, but [its] support structures (structs) …, with the help of methods and pointers, can help us achieve the same [outcomes].”
It looks to me like Go could be following in COBOL’s footsteps, but questions remain about where it’s going. In June 2019, RedMonk ranked Go in 16th place, with a future that could lead either direction.
What can Go learn from COBOL?
If Go were to see into its future, would it look like COBOL’s, with such staying power?
The stories told this season by Command Line Heroes illustrate how languages are born, how communities form around them, how they rise in popularity and standardize, and how some slowly decline. What can we learn about the lifespan of programming languages? Do they have a similar arc? Or do they differ?
This feature originally appeared in opensource.com