# I Killed Windows

> Leaving the long-running Windows install is the concrete version of every sovereignty metaphor on this site. Linux is legible. Open source is not weaker. Omarchy is an escape hatch, and the doctrine's rallying cry is not mine.

- Published: 2026-10-25
- Reading time: 7 min
- Source: original
- Canonical: https://reverb256.ca/posts/i-killed-windows/
- Markdown: https://reverb256.ca/posts/i-killed-windows.md

---

The metaphors were getting smug. Root, the admin password, tenants, people living inside a setup they cannot rebuild, firewalls and what they let in, rollbacks and the walk back to yesterday — fine words, every one, and every one a costume if the machine on the desk is still a long-running Windows install you are afraid to open. So I killed that arrangement. Not as a brand deal, not as a stunt. As practice. A machine should be legible to the person who lives with it, or that person is not living with it. They are renting.

[State as Operating System](/posts/state-as-operating-system/) already mapped the failure at the scale of a country. Windows ships a large default set, phones home about what the machine is doing, keeps its own update calendar, and makes removal expensive — and a state assembled the same way drifts in the same direction. The personal half of that argument is ruder. You do not get to write that essay and then shrug at the Start menu. [Solutions Over Problems](/posts/solutions-over-problems/) sets the standard: technology earns its keep only when the person who bears the cost can still read, change, and rebuild the configuration. If you cannot, you are not using a computer. You are using a kiosk with extra steps.

The test is embarrassingly practical: when the machine does something you did not ask for, can you find out why before the next update? Can you point at the process, read the unit file, change the line, and put it back? If the answer is "I would have to search for a forum post and hope", the machine is not yours in any sense that survives a warranty. It is a service you have been allowed to keep in your house.

## Linux Reads

"There's an elegant simplicity and human readability to the logic and flow of Linux." Human readability is the whole ethic. A config you can say out loud is a config you can argue with. A settings pane with three cheerful sliders and the real behaviour hidden in a signed blob behind them is a conversation with a mascot. I like mascots. I do not let them hold root.

The elegance is not minimalism as a cult; it is that cause and effect sit close enough to touch. You change a line, and the machine changes. You hate the change, and you revert the line. Yesterday is not a favour from a vendor's rollback fairy. It is a file you kept.

The first time you break your own install and fix it from a TTY, something changes in your relationship with the hardware: the fear goes out of it. A broken config stops being an emergency and becomes a puzzle with a known shape, and you discover that most of the "expert" mysteries were just paths and permissions nobody had shown you.

[The Sysadmin Protocol](/posts/the-sysadmin-protocol/) calls this intimacy permissions, and the line at its heart was never a metaphor: "That gap is the command line. And accreting agency is the realization that you can type sudo su and claim root access to your own hardware." The guest stares at the pane. The person who runs the machine reads the file. I had grown tired of being the guest on hardware I paid for.

## Open Source Is Not the Soft Target

The superstition says visible code is vulnerable code, and the superstition is a sales pitch. "Open source does not mean more vulnerable." The pitch also arrives far too late to be coherent: "Every piece of software you use depends on some free and open source components." The closed platform is not a clean artefact from a sealed lab. It is paint over a stack the vendor did not entirely write and will not let you patch on your own schedule. The vulnerability was never the public diff. The vulnerability is the permission you need before you are allowed to respond to it.

A bug in the open is a bug you can pay a stranger to fix on a Saturday morning. A bug in the sealed blob is a bug you report, and wait on, and thank someone for when it finally reaches their calendar. The waiting is not the worst part.

The worst part is the silence in between, where you cannot tell whether the report was read, disputed, or quietly closed, and you keep using the machine as if the answer might arrive. Open code turns that silence into a thread you can read, and a fix you can apply yourself if the maintainer is busy, asleep, or no longer interested. Waiting is sometimes wise. Waiting as a permanent architecture is learned helplessness with a taskbar. [Crypto Is FOSS for Value](/posts/crypto-is-foss-for-value/) lifts the same superstition off the desktop and sets it on the ledger, where closed does not mean safe either. Closed means you hear about the hole when the admin feels like posting.

## The Escape Hatch, and Whose Cry It Is

Omarchy is the hatch I actually trust for this job: a curated Linux you can still inspect and still change, defaults somebody chose that you can still open. I have been blunt about why. "Omarchy is the operating system most likely to be your Escape Hatch From Digital Tyranny." And, because tools are also culture: "What they don't get is that like the iPod, Omarchy is a cultural movement." A movement is allowed. A movement is not a personality you install without reading.

The doctrine's heading, "Unite the nerds," belongs to [the Omarchy Doctrine](https://omarchy.org/doctrine/). That page is DHH's, and the cry is his. I am glad the cry exists, and I am not going to cosplay as its author, any more than I let a model cosplay as mine. Use the hatch, credit the sign above the door, then change the config until the machine matches the life instead of the brochure.


A movement that forbids a local diff has become the thing it was leaving. The health test for any tool culture is whether the weird fork is welcomed or hunted. Somebody will always want the panel on the other side, the keybinding that makes sense to their hands, the daemon they do not need. A culture that answers that with a config file is alive. A culture that answers it with a support ticket and a tone of disappointment has already become an appliance.

## A Fleet You Can Rebuild

I am not publishing a rack diagram, a hostname, or a count of boxes. The topology is not the lesson. The lesson is that a fleet you can rebuild from a description is a fleet you own, and a fleet you can only reboot by ritual owns you.

Repair belongs in the same sentence. A loose connector, a tired fan, a tracker that needs a base station: these are not hobbies adjacent to sovereignty. They are sovereignty with grease on it. In the VR years the log was cheerful and specific. "I use full body tracking with Tundra trackers, which also requires SteamVR base stations." "Beat Saber has some primo beatmaps." The beatmap and the tracker are the same muscle: you learn the system by touching it until it works, without filing a ticket with the universe.

[The Dojo Kun Is a Permissions Model](/posts/the-dojo-kun/) is the older name for that muscle — character, effort, self-control. You do not get a readable machine by wanting one. You get it through the unglamorous reps: the line you read, the part you replace, the driver you refuse. [Private Worlds](/posts/private-worlds/) is where a great deal of the joy of that tinkering ended up sitting down beside another person, and the hardware was never the opposite of the room. The hardware was how the room became possible.

That is the part the metaphors keep missing: all of this tinkering is not a hobby that competes with a life, it is the maintenance that makes the life possible. The tracker that needs a base station, the fan you replace at midnight, the install you rebuild on a Sunday afternoon — none of it is the point, and all of it is the reason the point can happen.

Kill the install you cannot read. Keep the one that answers when you ask it a question. The desktop is not a lifestyle; it is the first config. Every other metaphor on this site is a liar if that one is still a tenant agreement, a rental where somebody else holds the keys.

Related: [State as Operating System](/posts/state-as-operating-system/) · [Solutions Over Problems](/posts/solutions-over-problems/) · [The Sysadmin Protocol](/posts/the-sysadmin-protocol/) · [Crypto Is FOSS for Value](/posts/crypto-is-foss-for-value/) · [Open Weights Are Data](/posts/open-weights-are-data/) · [Lawful Access Is a Backdoor](/posts/lawful-access-is-a-backdoor/) · [The Dojo Kun Is a Permissions Model](/posts/the-dojo-kun/) · [Private Worlds](/posts/private-worlds/) · [Respawn Discipline](/posts/respawn-discipline/)

Further reading: [the Omarchy Doctrine](https://omarchy.org/doctrine/), theirs, including "Unite the nerds."
