I Killed Windows

The metaphors were getting smug. Root, tenants, firewalls, rollbacks: fine words, every one of them, and every one of them a costume if the machine sitting 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 and not as a stunt, but as a practice, because the box should be legible to the person who lives with it, or that person does not really live with it at all. They rent it.

State as Operating System already mapped the failure mode at the scale of a country. Windows ships a large default set, phones home, enforces its own update calendar, and makes removal expensive, and a state built with the same composition method drifts in exactly 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 sets the standard, that technology earns its keep only when the person who bears the cost can still read, modify, and rebuild the configuration. If you cannot, you are not using a computer; you are using a kiosk with extra steps.

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 that a person can speak out loud is a config that can be argued with, while a settings pane that offers three cheerful sliders, as the real behaviour hides in a signed blob behind it, is nothing more than a conversation with a mascot. I like mascots. I do not let them hold root.

The elegance is not minimalism as an aesthetic cult; it is that cause and effect sit close enough together to touch. You change a line, and the machine changes. You hate the change, and you revert the line. Prior state is not a favour granted by a vendor’s rollback fairy; it is a file you kept. The Sysadmin Protocol describes this intimacy as permissions, and the command 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 admin reads the file; and I had grown tired of being the guest on hardware I had paid for.

Open Source Is Not the Soft Target

The superstition says that visible code is vulnerable code, and the superstition is a sales pitch. “Open source does not mean more vulnerable.” And the pitch arrives far too late to be coherent anyway: “Every piece of software you use depends on some free and open source components.” The closed platform is not a pure artifact delivered from a sealed lab. It is a coat of paint over a stack the vendor did not entirely write and will not let you patch on your own timetable. 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 hire a stranger to fix on a Saturday morning; a bug in the sealed blob is a bug you can report, and then wait on, and then thank someone for when it finally appears on their calendar. Waiting is sometimes wise. Waiting as a permanent architecture is learned helplessness with a taskbar. Crypto Is FOSS for Value lifts the same superstition off the desktop and sets it down on the ledger, where closed does not mean “safe” either. Closed means “you will hear about the hole when the admin feels like posting.”

The Escape Hatch, and Whose Cry It Is

Omarchy is the practical hatch I actually trust for this job: a curated Linux you can still inspect and still change. 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 own heading, “Unite the nerds,” belongs to the Omarchy Doctrine. That page is DHH’s, and the rallying 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, and then change the config until the machine matches the life rather than the brochure, because a cultural movement that forbids a local diff has become the very thing it was trying to leave.

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 is a fleet that 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 specific and cheerful. “I use full body tracking with Tundra trackers, which also requires SteamVR base stations.” “Beat Saber has some primo charts.” The chart and the tracker are the same muscle, and you learn the system by touching it until it works, without ever filing a ticket with the universe.

The Dojo Kun Is a Permissions Model 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 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.

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, and every other metaphor on this site is a liar if that one is still a tenant agreement.

Further reading: the Omarchy Doctrine, theirs, including “Unite the nerds.”