The Philosophical Developer — Ryoku: The Arch/Hyprland OS I Almost Skipped

I came off an immutable operating system — Fedora 43, sitting in the Universal Blue family — and I was not eager to trade one set of walls for another. The natural next candidate was Omarchy, the operating system DHH built. Polished, talked about, a desktop that just works out of the box. But the more I considered it, the less its opinions matched mine. I do not think it is a bad operating system; it is clearly good at what it sets out to do. I just do not want it anymore — and I believe the one I am working on now, Ryoku, is better. An Arch/Hyprland system that is open in exactly the way I wanted, and honest about what that costs.

What Ryoku actually is

Most of what I touch daily is a desktop shell on Arch. What Ryoku adds is structure around it. There is a map of the whole system — where every config lives, which binary owns it, how to reload it — kept current, in one place. Nothing is a guess. I stopped digging through dotfiles hoping to find the one that mattered; I read the map.

The bar and dock are not a fixed feature set. They are plugins. A widget I want is a file I add, not a setting I fight. The shell owns the keybindings, and it wires the pieces I actually use into real bindings rather than shipping a wall of defaults.

Dictation is a first-class citizen, not an afterthought. Voxtype is bolted in, a mic wave on top of the bar, one key away. I did not have to assemble a speech-to-text stack; it was already there, running.

Kept clean on purpose

The reason the base system can be minimal is that everything risky lives somewhere else. All my experimental work happens inside distrobox containers — the playgrounds, the toolchains, the half-baked ideas. That is not going to change; it is how I keep the experiments from polluting the host. My local user services run as Podman quadlets, small declarative units that come up with the machine and stay in their own sandboxes.

Most of what I run is containerized most of the time. The operating system underneath stays lean, static, and boring — which is exactly what an OS should be. Ryoku is the shell over that. It does not try to be the container layer or the service layer; it just wires the desktop cleanly on top of a host I can keep clean because I almost never have to touch it directly.

The honest bit

It is not stable. Not in the way a distro aimed at “it just works” is. There are rough edges, corners where an upstream update outruns the packaging, days where I am the one debugging a reload. I have been using it a short while and I already know where the sharp parts are.

But it is dramatically better than where I was. The system I came from — Fedora 43 on an immutable base, part of the Universal Blue family — is going through a rough transition right now. The move between Fedora 43 and 44 has genuinely not been solid; the updates are not as reliable as I want them to be at the moment. So I stepped sideways. Here is the difference that matters: when something is rough on Ryoku, I can fix it. The structure is open enough that the fix is mine to make and keep. That is not true of the polished alternative. Opinionated systems are comfortable until the day you disagree with them, and then they are walls.

The decision

This was never about polish. It was about who owns the machine. Omarchy sets out to be a good-looking, opinionated desktop and does that honestly — those opinions just are not mine. Ryoku gives me a desktop that is sometimes rough and always mine. For what I build, that is the only trade that matters.

Honestly? Part of why I moved was an excuse. I wanted to run Ryoku, and the update trouble gave me the nudge I needed. I am glad it did. I am not planning to stay here as a permanent home — I will go back to an immutable operating system, because that way of thinking is mine; the base should be solid, quiet, and closed, and I agree with it. But in the meantime I can use Ryoku just fine, and it has shown me something worth keeping. The best operating system is a solid base with a personality layered on as an extension. That is the idea I take back with me.