You’ve probably felt it. That itch to build your own programming language. The one that fixes everything that’s wrong with JavaScript, Python, and Rust. But you looked at the compiler toolchain, saw the mountains of C++ and LLVM, and closed the tab.
I get it. Building a language from scratch sounds like a PhD thesis, not a weekend project. The gatekeepers told you need a team, a budget, and years of systems programming experience. They lied.
Here’s what actually happened: a developer named codemplasi posted a single batch script on Codeberg. That script compiles QBE — a minimalist compiler backend — on Windows. That’s it. That’s the whole secret.
You don’t need a billion-dollar IDE or a corporate lab to create the next language revolution. You need a Windows machine, a batch file, and a stubborn refusal to accept that this should be hard.
QBE is a tiny, fast compiler backend that generates efficient machine code. It’s been around for years, but the barrier was always cross-compilation or Linux-only setups. This batch script changes everything. Now, any solo developer on Windows can spin up a backend in minutes.
I watched a developer on Hacker News share the link. The comments lit up. People who had given up on language design suddenly had hope. One guy said, ‘I’ve been wanting to build a language for five years. This script made it possible in an afternoon.’
Think about what that means. The next dominant programming language — the one that might replace Python or JavaScript — isn’t being designed in a Google conference room. It’s being sketched on a notepad in a bedroom, powered by a batch script that removes the gatekeepers.
The most powerful tool in software development isn’t a billion-dollar IDE. It’s a single script that says: ‘You are allowed to build this.’
We’ve been sold a story that making a language is rocket science. It’s not. It’s a batch script that downloads a few dependencies and runs make. The real science is the ideas you encode in the syntax, the semantics, the community. The backend is just plumbing.
So stop waiting for permission. Grab the script. Download QBE. Start writing your language. The world doesn’t need another corporate-backed framework. It needs the weird, beautiful, opinionated language that only you can build.
Neutrality is death in language design too. Take a side. Build something that makes people feel something. And do it on a Windows laptop with a batch file.
FAQ
Q: Is QBE really capable of production-quality code generation?
A: QBE is minimal but production-ready for many use cases. It's used in real projects like Hare and a few embedded systems. It may not match LLVM's optimization passes, but for a new language targeting performance-critical or embedded applications, it's more than enough. The simplicity also means fewer bugs and faster compile times.
Q: What does this batch script mean for me as a developer?
A: It means you can prototype a new language in a weekend without setting up a cross-compilation environment or learning arcane build systems. Just download the script, run it on Windows, and you have a working compiler backend. You can focus on syntax, semantics, and the unique features of your language instead of fighting toolchains.
Q: Isn't this just a toy? Real languages need LLVM.
A: LLVM is overkill for 90% of language experiments. Many successful languages, including early versions of Go and Rust, started with simpler backends. QBE forces you to think about code generation from first principles, which often leads to cleaner language design. Don't let the allure of 'enterprise-grade' tooling be an excuse to not start.