Imagine dusting off a 30-year-old operating system designed for a custom CPU that nobody uses anymore. Then imagine running it on a $10 RISC‑V board you bought off AliExpress. That’s not a fantasy — it’s exactly what Rochus Keller just did. And it changes everything about how we think about retro computing, portability, and software that refuses to die.
Project Oberon, Niklaus Wirth’s masterpiece of minimalism, was born on a custom RISC‑5 processor. For decades, running it meant hunting down scarce FPGA boards or emulators that replicated that exact chip. The common assumption? Oberon is tied to RISC‑5 — love it or leave it.
That assumption is wrong. Oberon’s genius was never its CPU. It was the discipline of doing more with less. The port to RISC‑V proves that the real essence of the system is its radical simplicity, not the instruction set it happened to run on. By stripping away the hardware dependency, Keller has shown that any clean, open ISA can become a viable host.
You’ve probably seen the endless debates about FPGA vs. emulation, about preserving original hardware at all costs. But the real bottleneck isn’t the die — it’s the toolchain and the ability to self‑host. One comment on the HN thread nailed it: “Would it be practical to have the ESP32‑P4 self‑host?” That’s the question that matters. If Oberon can compile itself on a commodity microcontroller, it becomes immortal — not a museum piece.
Purists will argue that porting to RISC‑V betrays the original vision. They’re wrong. The port proves that a 30-year-old design can still teach us something about software simplicity. Wirth’s goal was never to enshrine a particular chip; it was to build a system so clean that it could be understood by one person. That philosophy survives exactly because it’s adaptable.
So here’s the takeaway: stop obsessing over CPUs. The future of retro systems isn’t in preserving hardware — it’s in preserving design principles. Oberon on RISC‑V is a concrete case study in portable system design. It’s an invitation to run an elegant, ultra‑minimal OS on the cheapest, most open hardware available today.
Grab a RISC‑V board, clone the repo, and see for yourself. The future of Oberon isn’t in a museum — it’s on your desk.
FAQ
Q: Isn't this just a novelty? Why would anyone use Oberon today?
A: It's a proof of concept in minimalism. Oberon's simple design is a learning tool and a counterexample to bloated systems. It runs on minimal hardware, making it useful for embedded systems where every byte counts.
Q: What's the practical implication for someone building a system today?
A: The takeaway is that separating hardware and software design is key. If you keep your OS independent of any single ISA, it can survive hardware shifts. Oberon's port is a blueprint for portable system design.
Q: Is the port actually a betrayal of Oberon's original vision?
A: The original vision was simplicity and elegance, not RISC-5. Adapting to RISC-V is the most faithful way to keep that vision alive. Betrayal would be letting the system die on a dead architecture.