COBOL’s Continuing Credentials
When an opportunity to discuss COBOL in a public forum arises, it proves to be an illuminating experience. The 2026 GSE Nordic conference in Helsinki was no exception.
Incomparable, or contemptible?
For years, COBOL has been treated by some as a technology punchline in technology circles, typically alongside labels such as “old,” “legacy,” or “outdated.”
Elsewhere, the accepted wisdom is that COBOL remains one of the most consequential languages in enterprise computing, because it continues to deliver where reliability, clarity, and business performance matter most.
That distinction is important. Thought leadership is often about separating noise from the truth, and in COBOL’s case, the noise has lasted for decades. The truth is much more practical: COBOL continues to underpin core systems in banking, insurance, government, retail, manufacturing, and healthcare. An estimated 250 to 800 billion lines of COBOL is still in use, and COBOL remains within the top 30 programming languages. They are the markers of a language with enduring enterprise value and enduring strength.
Hidden Superpowers
Statistics aside, that power is more than just rhetoric or sentiment. The operational reality of how COBOL has evolved, thrived, and supported such commercial success, is built on solid foundations.
Perhaps greatest strength is that it was built for business (that’s what the B stands for). Enterprise systems still depend on precise arithmetic, structured records, predictable execution, and high-volume transaction handling. Those requirements remain exactly what many large organizations need today. And when tech stays aligned with the business problem it was designed to solve, longevity is entirely feasible.
In addition, in COBOL’s long-term favour is that its English-like structure (a core element of its original specification) makes it easy to understand and maintain. In mission-critical systems, readability is a strategic enabler. Clear logic reduces operational risk, supports maintenance, and helps teams work more effectively across long-lived applications. After all, the value of the code is what it does, not how it looks. Concise code is useless if nobody understands it.
COBOL’s tenure also mandated a high-level of adaptability. COBOL systems today can connect with APIs, modern databases, containerized environments, and operate as part of broader cloud-enabled strategies. COBOL was never the island its critics suggested.
Finally, a word on portability. COBOL is perceived as mainframe-specific, but was designed as machine-independent, happily running across countless platforms, from mainframe to Linux to cloud and beyond. That architectural flexibility explains why it has survived multiple infrastructure eras. Technologies that persist at scale do so because they can navigate environmental tectonic shifts.
Fighting Against Fallacy
Sadly, what undermines COBOL back today is a question of perception. Fables and fairy-tales about COBOL require a mature, measured review, to fight back. Notorious myths that need busting include –
- COBOL is old and no longer invested in. Let’s be clear – age is not the same as abandonment, and nor is it an indicator of a lack of investment. Vendor support continues, standards development continues, tooling continues to evolve. The fact is that COBOL’s impressive tenure remains underpinned by a healthy, living ecosystem.
- COBOL is too verbose to be practical. But verbosity and unreadability are not the same thing. In many enterprise contexts, explicitness is an advantage. Systems that run payroll, process claims, reconcile accounts, all rely on logic that can be followed and maintained. Complexity exists in every language, in every large-scale codebase.
- The COBOL skills gap makes the language untenable. While a serious concern, it merely reflects that organizations need to treat knowledge transfer, training, and workforce planning as strategic priorities. Every critical technology stack requires stewardship, and COBOL is not unique in that regard.
- It has no place in the cloud era or the AI era. These ideas reflect a narrow view of modernization. Cloud is not simply about replacing everything old with something new; it is about designing flexible, resilient, economically sensible systems. AI is not only about greenfield development; it is also about documentation, code understanding, testing, modernization support, and extracting and accelerating fresh value from long-lived assets. On both fronts, COBOL can be part of that future.
- It is Technically Deficient for the Modern Era. Is it? A common complaint bemoans global variables in COBOL. However, the local-storage capability has been part of the language for years. COBOL is updated annually by vendors, while the latest standard is a couple of years old. Idle criticisms of COBOL betray assumptions that are out of date or borne out of preference or prejudice.
Technology Leaders, Take Note
Organizational success tends not to depend on fashions or trends. The most useful leadership question is whether COBOL continues to create business value. And in many environments, not least the enterprise-scale commercial world, the answer is commonly yes. That should shape how leaders think about modernization of their most important IT systems. Too often, so-called experts frame the issue as a binary choice between preserving COBOL untouched or replacing it entirely. A more intelligent strategy is to evaluate where COBOL remains the right engine, where evolution, innovation, and integration can extend its value, and where targeted modernization can reduce risk without discarding what still works.
If leaders continue to treat COBOL as a fairy story from another age, they risk making poor decisions based on image rather than evidence. If they recognize it as a proven business language with modern relevance, they can make sharper choices about talent, tooling, architecture, and transformation. After all, COBOL’s credentials are stronger than any ill-informed reputation suggests. Its scale of deployment, business alignment, readability, portability, and compatibility with modern environments all point to the same conclusion: COBOL still means business.
There’s no place for either bias or nostalgia in IT strategy. Durable technologies endure because they offer long-term viability for critical commercial systems.
Longevity, paired with relevance, is a strategic strength. And that’s no fairy-tale.
