Why I keep a boring Linux daily driver
Flashy distros come and go. A plain setup that survives upgrades is worth more than another rice screenshot.
Every few months someone asks which Linux distro will finally make the desktop “just work,” and I always give the same unsatisfying answer: the one you can maintain for three years without reinstalling.
I am not against experimentation. I have run plenty of rolling releases, tiling window managers, and custom kernels. But the machine I actually write on is deliberately dull. It uses a stable base, a small set of packages I understand, and backups that restore in one afternoon.
What “boring” means in practice
I use a long-term-support or slow-rolling base I trust to ship security fixes without breaking my toolchain. Configuration lives in plain text under version control, not buried in a GUI I cannot diff. I stick with one window manager or desktop long enough to stop fighting it.
When a deadline is close, I want predictability, not minimalism for its own sake. I do not want to debug why Bluetooth stopped working after a theme update.
Omarchy on the daily driver
I run Omarchy on the Linux box I use every day. Arch and Hyprland, assembled by DHH and the Basecamp crew into a single opinionated desktop. The hardware is a home-built machine, roughly Framework-class, and it has survived the kind of weeks where I cannot afford a surprise reinstall.
I like the defaults. The thousand small decisions someone else already made let me open a terminal and get back to work instead of ricing for another weekend. I keep my configs in plain text and I know how to rebuild the skeleton if I have to. Omarchy earned the slot because it stays out of the way while I write.
The question I ask before changing anything
Will this still make sense after the next major upgrade?
If the answer is no, it waits until the weekend or it does not ship at all.