When I started Kobol, I wasn't trying to build the most powerful language in the room. I was trying to build one more people could actually read. There's a long tradition behind that choice. The early business languages were built on a simple idea: that everyday people — not only trained specialists — should be able to sit down at a computer and get real work done. That idea still holds up, and I built Kobol around it. Plain words first. Kobol is written in everyday English as much as a language can be. You say what you mean — DISPLAY, ADD, MOVE, FOR EACH — and the program does that thing. If you can describe the work in a sentence, you're most of the way to writing it. I'd rather you spend your thinking on the problem in front of you than on decoding punctuation. Less like a math proof, more like a memo. A lot of languages ask you to think like a mathematician before you've thought like a person. Kobol doesn't. The code is shaped like the work it describes: records that look like the forms on your desk, steps that read from top to bottom, money that adds up the way money is supposed to. You don't need a background in symbols and theory to get something useful done here. Easy to pick up, even when that costs some power. This is a real trade, and I made it on purpose. There are sharper, shorter languages out there, and for some jobs they're the right call. Kobol chooses the gentle slope. If staying approachable means leaving a clever shortcut on the table, that's a price I'll pay. A tool more people can use beats a tool fewer people can show off with. Open the door wider. The best ideas for a program often live in the heads of the people closest to the work — the ones who know the invoices, the payroll, the rules — not only the people who write code for a living. Kobol is built so those two groups can meet in the same file and both follow it. The fewer people it shuts out, the better the software gets. Neutral by design. Kobol isn't here to win an argument about how software "should" be written, and it isn't tied to any one vendor or platform. It runs on the JVM because the JVM runs nearly everywhere — a practical choice, not a statement. You should be able to bring it into your work on its own terms, and judge it on whether it helps. That's the whole project, really. Keep it readable. Keep it honest about numbers. Keep the door open. Everything else — the JVM speed, the Java interop, the concurrency, the testing built right in — is there to serve those few simple promises. I'm glad you're here. Come build something anyone can read.

Kobol

A Modern COBOL-Inspired Language for the JVM

A Modern COBOL-Inspired Language for the JVM