Somewhere between a joke and a monument to stubborn engineering sits COBOL on Wheelchair — a micro web framework for a language that predates the web by roughly three decades. The name is a knowing wink at Ruby on Rails, and the project delivers exactly what it promises: routes, templates, and HTTP handling written in a language whose primary users today are still running batch jobs at banks and insurance companies.

Why should a technical audience care about a repo that looks, at first glance, like a punchline? A few reasons:

• COBOL is not dead — it is load-bearing. Estimates put the amount of COBOL in production somewhere between 200 and 800 billion lines, running the backend of most of the world's ATM transactions, payroll systems, and government benefits. Projects that bring modern paradigms to COBOL aren't nostalgia — they are one of the few bridges keeping legacy systems reachable from the modern web without a full rewrite.
• It's a genuine architectural exercise. Building a routing layer in a language with no closures, no first-class functions, and fixed-column source formatting forces you to think about what a web framework actually is when you strip away the ergonomic sugar. It's the sort of constraint-driven design that reveals how much of modern frameworks is convention rather than necessity.
• It's a teaching tool. For anyone who has only ever met COBOL through mainframe migration horror stories, seeing it wired up to CGI and HTML makes the language legible in a way that PIC clauses and PERFORM UNTIL loops in isolation never do.

The project leans into its absurdity — the repo name alone is a commitment to the bit — but the underlying craft is real. Wiring GnuCOBOL to a CGI handler, defining a template DSL inside COPY files, and making it feel almost ergonomic is the kind of thing that requires deep familiarity with both worlds.

It also lands at an interesting moment: with LLMs newly able to read and translate COBOL at scale, the language is quietly having a second wind in tooling. Small projects like this become reference points — canonical examples of how to graft modern shapes onto ancient runtimes without demanding a full migration.

Worth a star, worth a read, worth thinking about the next time someone claims a legacy system "can't" do something.