You know that feeling when your laptop takes 30 seconds to boot, and you’re just trying to open a text editor? Here’s a mind-bender: a 1980s operating system, designed to run on hardware with 2MB of RAM, can do everything you need—and do it instantly.
It’s called CP/M-386. A resurrected version of the old CP/M, ported to run on 386 protected mode. The GitHub repo is a quiet tombstone of what computing used to be. And it’s a damning indictment of where we’ve ended up.
The software industry has spent 40 years convincing us we need more power, while quietly burning that power on nothing.
Modern operating systems are engineering marvels—if you measure them by lines of code. Windows 11? Hundreds of millions of lines. macOS? Similar. Even a lightweight Linux distribution ships with a kernel that’s tens of millions of lines. And they all demand 8GB of RAM just to breathe. Yet for the basic tasks people actually do—file management, word processing, web browsing—they feel less responsive than a machine that had 2MB of RAM and a 40 MHz processor.
That’s not progress. That’s a tax.
I dug into the CP/M-386 source code. It’s a masterclass in doing more with less. The entire OS, with a full command-line interface, file system, and multitasking support, fits in a fraction of the memory that a modern browser uses to render a single ad. It boots in milliseconds. It doesn’t have a ‘loading’ spinner. It just works.
But here’s the dirty secret: the fundamental needs of a personal computer haven’t changed since the 1980s. We still need a file system, a command line, a way to run programs. That’s it. Everything else is overhead—compatibility layers, telemetry, cloud integrations, animations, 20 different background services all fighting for the same CPU cycle.
One comment on the repo says it best: “An order of magnitude (or two!) less code complexity and less memory hungry than most of 2026’s bloated Operating Systems… Well done!” That’s a random developer on the internet, not a retro nostalgist. They’re pointing out what we’ve all been too polite to say: we’ve been sold a lie.
I’m not saying we should all go back to green text on a black screen. But I am saying that the industry’s obsession with abstraction layers and backward compatibility has created a ‘complexity debt’ that makes modern systems fundamentally fragile. Every new feature adds another layer of indirection, another translation from high-level API to low-level hardware. And each layer burns power, memory, and time.
We’ve been sold a narrative of progress, but progress measured in features is not the same as progress measured in efficiency.
Think about the last time you rebooted your computer because it was ‘acting weird.’ That weirdness is a symptom of a system that has become too complex for anyone to fully understand. CP/M-386, by contrast, is simple enough that a single developer can hold the entire operating system in their head. It’s understandable.
There’s a reason the repo description says ‘Compatible with 386 (and later systems) with 2MB (or more) memory.’ That’s not a limitation—it’s a feature. It means the OS doesn’t need a nuclear reactor to run a text editor.
Next time you watch your computer spin its wheels, ask yourself: what are you actually paying for? The answer might be a 40-year-old operating system that fits in a floppy disk.
FAQ
Q: Isn't CP/M-386 just a toy for retro enthusiasts? What's the real-world relevance?
A: It's a proof of concept that modern OS bloat is not inevitable. The same principles apply to cloud infrastructure, embedded systems, and even mobile apps. The real question is whether we've accepted unnecessary complexity as normal.
Q: Why would anyone want to use CP/M-386 today? It lacks modern features like networking, graphical interfaces, and security.
A: That's exactly the point. The analysis shows that for many basic tasks (file management, text editing, command-line tools), the extra features of modern OSes are not just unnecessary—they actively degrade performance and reliability. The trade-off is worth questioning.
Q: Aren't modern OSes more secure and capable? CP/M had no memory protection or multitasking.
A: The 386 protected mode version of CP/M does have memory protection and multitasking. And modern OS security largely comes from complexity, which also introduces new vulnerabilities. The article argues that we've confused capability with bloat—true capability comes from elegant design, not layers of abstraction.