The Framebuffer People: I Cloned Every OS on r/osdev and Found Five Real OnesSkip to main content▶ BRIDGE◆ MISSION LOGS● MARS⬟ CHRONICLES⚡ Liberation🛡️ Shield Protocols🔧 Liberation Tools<br>░ DATA DEBRIS◈ CREW LOG<br>XGitHub

Two Months of git clone¶

For two months, every time someone posted an operating system on r/osdev, I cloned it. Then I ran the code through an analyzer. Not vibes. Tooling.

Here is what came out the other end:

Projects with a genuinely different architecture: I can count them on one hand.

Everything else: a reskin of a reskin, which was itself based on Linux.

Projects that boot on real hardware: almost none. They live in QEMU. They were born in QEMU. They will die in QEMU.

I also talked with the authors. Most of the time they could not explain what they were building. I watched 20-year-olds implement ISA slots that were obsolete before they were born. Hand-rolled SHA256 “because the library is bloated.” Feature roadmaps with PCMCIA support, Motorola modem support, and USB 1.1, generated by a model that clearly pulled its ambitions from a 1997 Packard Bell.

On Discord I ran a small experiment. I baited one of these authors: “Ah, you forgot the SCSI and PATA drivers.” His answer came back instantly: “Planned. Already have it in mind.” I found out later he was born the same year PATA was deprecated. He had no IDEa what I was talking about.

My favorite artifact: a commit that said “this computer has no BIOS, skipping this,” pushed to GitHub, followed by a revert two minutes later. That is an AI hallucinating mid-task, and a human rubber-stamping the hallucination into version control without reading it.

What is actually missing from the hobby OS world is drivers. Nobody writes drivers, because everyone lives in a framebuffer. Not one OS posted in that sub has a WiFi or Bluetooth stack. But they have websites. Beautiful websites. Discord servers. Some have Patreon.

So I posted the findings. 115 upvotes, 137 comments, and several public meltdowns later, I learned that the reactions were more diagnostic than the code.

The thread is here if you want to watch it live.

The Five Defenses¶

Every reply fell into one of five buckets. Save this taxonomy. You will see it in every hobby community that AI touches.

1. “Stop gatekeeping my hobby”¶

The most popular one. Note what I actually asked for: nothing. No bans, no rule changes, no fork of the community. I published an observation. The people who felt attacked self-selected.

If you play GTA V, you don’t tell people your hobby is racing and heists. You tell them your hobby is gaming. If you play Call of Duty, you don’t claim you went to war or plotted a strategy. It’s the same map, over and over, with the same enemies that want to mount your mom, ten thousand times. There is nothing wrong with either. Just don’t confuse the simulator with the real thing.

2. “Old man yells at cloud”¶

Fine. But one commenter asked the question that none of the cloud-yelling accusations could survive: if this is your hobby, why do you outsource it to an AI? Nobody outsources their guitar practice. Nobody hires someone to do their jogging.

The answer, once you strip the noise: the hobby is the attention. The OS is just the costume. They all want to be Terry Davis without the schizophrenia, and it turns out the schizophrenia was the part writing the compiler.

3. “It’s creepy that you cloned our repos”¶

Someone genuinely argued that running git clone on publicly posted repositories, the thing the entire open source ecosystem is built on, was creepy behavior. Public code, posted publicly, for the stated purpose of being seen. Reading it closely was the violation.

This tells you what the repository actually is. It is a poster, and I committed the crime of checking whether the movie exists.

4. “Share YOUR project then”¶

The credentialism reflex. My work lands in proper operating systems. I have commits in Linux, in FreeBSD, in DragonFly BSD. Small fixes, uncredited on any landing page, with no Discord server attached.

I have none in NetBSD or OpenBSD. NetBSD runs on some of my NASes and OpenBSD sits in my firewall, but I don’t live in them daily, so I don’t have the knowledge to contribute there yet. Notice the word yet. Yesterday I finished reading FreeBSD Device Drivers. It took around 200 days, exactly as I predicted when I started. That is what the on-ramp to contribution actually looks like: 200 days of reading before you touch a subsystem, and the honesty to say “not yet” about systems you merely operate. That is the friction the framebuffer people skipped.

5. “This post was written by an LLM”¶

The best one. In a subreddit drowning in AI-generated kernels, the accusation that finally landed on me was that my prose was too structured to be human.

No bro. You have it backwards. The LLM writes like me. Structure is what non-native English speakers learned so English people would understand us. I can’t speak like Eminem, but I can write with spaces...