COBOL at 65: The Immortal Language That Still Runs the World

From a 1959 Pentagon meeting to GCC 15.1 — how a six-decade-old language refuses to retire

BJ
Bob James
6 min read
1 votes
0 comments

COBOL has been declared dead more times than any language in history, yet it still processes an estimated 95% of ATM transactions and 80% of in-person transactions globally. With GCC 15.1 shipping a brand-new COBOL frontend, the language's story is far from over.

COBOL — the COmmon Business-Oriented Language — is more than 65 years old, and it is not slowing down. First appearing in 1960, COBOL remains one of the most consequential programming languages ever created. An estimated 220 billion lines of COBOL are still in active use today, underpinning the financial systems, government agencies, and insurance companies that modern society depends on [^1]. In 2025, the GNU Compiler Collection (GCC) cemented COBOL's relevance by shipping a brand-new COBOL frontend, gcobol, with its 15.1 release — the first new language frontend added to GCC in over a decade [^2].

Origins: A Meeting at the Pentagon

COBOL's story begins on May 28–29, 1959, when a group of computer scientists, military officials, and industry representatives gathered at the Pentagon for a meeting convened by the United States Department of Defense. Their mission was ambitious: design a portable, business-oriented programming language that could run on hardware from different manufacturers [^3].

The result was the Conference on Data Systems Languages (CODASYL) committee, which produced the initial COBOL specification by the end of that year. The language first appeared in 1960, and by 1970 it had become the most widely used programming language in the world [^3].

The People Behind COBOL

COBOL was shaped by a remarkable committee of designers:

  • Howard Bromberg — contributed to the language specification and is famously said to have expressed his frustration with the naming process by buying a $15 tombstone engraved with "COBOL" [^4]
  • Norman Discount — worked on the language's data description capabilities
  • Vernon Reeves — contributed to the procedural division design
  • Jean E. Sammet — a key designer who later wrote the definitive early history of COBOL and served as an ACM president [^5]
  • William Selden — contributed to the specification at RCA
  • Gertrude Tierney — worked on the language design at IBM

The indirect but profound influence of Grace Hopper looms over the entire project. Hopper's earlier work on FLOW-MATIC (1955–1959), one of the first English-like programming languages, directly inspired COBOL's syntax and philosophy. FLOW-MATIC demonstrated that programs could be written in something resembling natural English rather than pure mathematical notation — an idea that became COBOL's defining characteristic [^6].

FLOW-MATIC: COBOL's Ancestor

FLOW-MATIC, developed by Grace Hopper and her team at Remington Rand, was the first programming language to use English-like keywords. Before FLOW-MATIC, programming languages were deeply mathematical in nature. Hopper believed that programming should be accessible to businesspeople, not just mathematicians [^6].

COBOL inherited this philosophy wholesale. Its verbose, English-like syntax — with statements like MOVE, ADD, PERFORM, and DISPLAY — was a deliberate design choice meant to make programs readable by managers and non-technical stakeholders. While modern developers sometimes mock this verbosity, it was revolutionary in 1960 and remains one reason COBOL code is relatively self-documenting [^3].

Language Characteristics

COBOL's programming paradigm has evolved over the decades:

Paradigm Description
Procedural The original and most widely used style of COBOL programming
Imperative Programs describe step-by-step instructions for the computer
Object-oriented Added in the COBOL 2002 standard [^7]
Generic Modern COBOL supports parameterized types and reusable constructs

The language has been standardized and maintained by multiple organizations over its lifetime:

  • CODASYL — the original committee that created and initially maintained the specification
  • ANSI — published the first formal COBOL standard (ANSI X3.23) in 1968
  • ISO/IEC — maintains the current international standard, with the most recent revision being ISO/IEC 1989:2023 [^7]

GCC 15.1: A New Chapter

Perhaps the most striking recent development in COBOL's story is the inclusion of gcobol, a native COBOL frontend, in GCC 15.1 (released in 2025). This makes COBOL a first-class citizen in the world's most widely used open-source compiler infrastructure, alongside C, C++, Fortran, Go, and Rust [^2].

The gcobol frontend allows COBOL programs to be compiled using the same toolchain and optimization pipeline as C and C++ programs. This is significant for several reasons:

  1. Performance — COBOL programs compiled with GCC can benefit from decades of optimization work in the GCC backend
  2. Interoperability — gcobol makes it easier to link COBOL code with C libraries and modern system APIs
  3. Accessibility — developers can now compile COBOL on any platform that GCC supports, without needing a proprietary COBOL compiler

Why COBOL Endures

COBOL's longevity is not an accident. Several factors explain why it remains entrenched:

  • Stability — COBOL programs written decades ago often still run correctly without modification
  • Decimal arithmetic — unlike most modern languages, COBOL handles fixed-point decimal arithmetic natively, making it ideal for financial calculations where floating-point errors are unacceptable [^1]
  • Massive installed base — the cost of rewriting hundreds of billions of lines of mission-critical COBOL would be staggering
  • Readability — the English-like syntax, while verbose, makes the business logic transparent

The COVID-19 pandemic in 2020 brought COBOL back into the public spotlight when several U.S. states struggled to process unemployment claims because their systems ran on aging COBOL programs and there were not enough COBOL programmers to maintain them [^8]. Rather than signaling COBOL's obsolescence, this episode demonstrated just how deeply embedded the language remains in critical infrastructure.

Conclusion

From a Pentagon conference room in 1959 to the GCC 15.1 release in 2025, COBOL has proven to be one of the most resilient technologies in the history of computing. With gcobol bringing it into the modern open-source compiler ecosystem, and billions of lines of COBOL still powering the world's financial systems, reports of the language's death remain greatly exaggerated.


References

[^1]: Joseph F. Cunningham "COBOL" Communications of the ACM, Volume 6, Issue 3 https://dl.acm.org/doi/10.1145/366274.366290

[^2]: Free Software Foundation. (2025). "GCC 15.1 Released." GCC Project. https://gcc.gnu.org/gcc-15/

[^3]: Sammet, J. E. (1978). "The Early History of COBOL." ACM SIGPLAN Notices, Volume 13, Issue 8 https://doi.org/10.1145/960118.808378

[^4]: Beyer, K. W. (2009). Grace Hopper and the Invention of the Information Age. MIT Press. ISBN 978-0-262-01310-9.

[^5]: Sammet, J. E. (1969). Programming Languages: History and Fundamentals. Prentice-Hall.

[^6]: United States. Navy Mathematical Computing (1954). "Automatic Programming — Definitions."

[^7]: ISO/IEC 1989:2023. Information technology — Programming languages, their environments and system software interfaces — Programming language COBOL. International Organization for Standardization.

Login to vote on this article

Share:

Discussion

Login to add a comment

No comments yet 🤯 but its such an awesome article.
Be the first to comment and start a discussion 🤗