Omarchy: How DHH's One-Minute Arch Linux Is Bringing the Opinionated PC Back
Setting up a new computer used to feel like a toll you paid before the machine would give you anything back. An hour and a half of Windows Update cycles and driver installs before a fresh PC is actually usable. Forty-five minutes of macOS updates, iCloud prompts, and migration screens before a new Mac stops asking questions. By the time either one is ready, the excitement of a new machine has usually curdled into the relief of having survived it. Omarchy, the opinionated Arch Linux distribution built by Ruby on Rails creator David Heinemeier Hansson – universally known as DHH – is a direct answer to that fatigue. Its pitch is almost rude in its simplicity: stop asking the user a thousand questions, make the right calls for them, and get out of the way in about a minute.
The Man Behind the Opinions
DHH needs little introduction to anyone who has shipped a web application in the last twenty years. He created Ruby on Rails, the framework that made “convention over configuration” a mainstream idea rather than an academic one, and he is the co-founder and CTO of 37signals, the company behind Basecamp and the email service HEY. Along the way he has built a reputation for opinions that are loud, public, and usually backed by code rather than just blog posts – from 37signals' well-documented exit from the public cloud back onto owned hardware, to his own very public move away from Apple hardware and macOS as his daily driver.
That last move mattered more than a simple laptop swap. DHH did not quietly switch operating systems; he documented the frustration that drove it – a sense that Apple and Microsoft increasingly treat the owner of a machine as a tenant of it – and then built the tools to make the same move easy for anyone else. Omakub came first, an opinionated setup script that turns a plain Ubuntu install into a fully configured developer machine. Omarchy is the same idea taken further: instead of layering opinions on top of Ubuntu, it builds them directly on top of Arch Linux, historically the distribution with the steepest and most manual setup of them all.
From Omakub to Omarchy
The name is a portmanteau of omakase – the Japanese “chef's choice” menu, where you trust the chef and eat what arrives – and Arch, the rolling-release Linux distribution long beloved by people willing to trade convenience for control. Omarchy takes the raw, unopinionated flexibility of Arch and wraps it in a single, curated set of decisions: Hyprland as the window manager, a consistent theme applied system-wide, a terminal-first toolchain, and a pre-selected set of developer applications, all installed and wired together by one command instead of by hand.
Omarchy's default desktop: Hyprland tiling, a curated theme, and a terminal-first layout – all present the moment the install finishes.
The Old Arch Tax, and the New One-Minute Boot
Installing Arch Linux the traditional way is something of a rite of passage in Linux culture – and not always an affectionate one. Partitioning disks by hand, choosing and installing a bootloader, wiring up networking, picking a window manager, and then configuring every dotfile from a blank canvas can easily eat an evening for a newcomer, and still takes real, deliberate time for an expert. That time-sink is exactly what Omarchy is built to remove. By DHH's own account, running the Omarchy install script against a fresh Arch base gets you to a fully themed, fully configured, ready-to-code desktop in roughly a minute – not a benchmark-lab number, but a genuinely small one next to the alternatives.
| Platform | Typical First-Boot Tax | What That Time Is Actually Spent On |
|---|---|---|
| Windows 11 | ~90 minutes (commonly reported) | Cumulative updates, driver downloads, OEM bloatware, account setup prompts |
| macOS | ~45 minutes (commonly reported) | System updates, Apple ID and iCloud setup, migration assistant, security prompts |
| Omarchy on Arch | ~1 minute (per DHH's own account) | Hyprland, theming, terminal, editor, and curated apps installed as one automated pass |
These figures are anecdotal rather than laboratory-measured – actual time varies with hardware, network speed, and how many updates happen to be queued that day. But the gap between “an evening of manual Arch configuration” and “about a minute” is the entire point: Omarchy is not trying to make Arch easier at the margins, it is trying to remove the setup tax altogether.
Three Reasons DHH's Opinions Actually Work
DHH has argued this exact case before, long before Omarchy existed. In his “Rails is Omakase” essay, he laid out why a framework – or, by extension, an operating system – benefits from having its choices made for you rather than offered as an endless menu. Three ideas from that argument carry straight over into Omarchy.
| Approach | What It Means in Practice | The Payoff |
|---|---|---|
| Trust the Chef | Window manager, theme, terminal, shell, and editor are all pre-chosen by someone who has already spent years tuning the combination | No decision fatigue before you have written a single line of code |
| Skip the À La Carte Tax | Every configurable option has a hidden cost – research, comparison, and eventual regret – that most setup guides never mention | That cognitive cost is paid once by DHH, not paid again by every single user |
| One Shared Language | Everyone running Omarchy is running roughly the same environment, the same keybindings, the same layout | Dotfiles, tutorials, and troubleshooting all transfer cleanly between users instead of “works on my machine” territory |
The easiest misreading of “opinionated” is to hear “restrictive.” What it actually means, in the Omakase tradition DHH has argued for since his Rails days, is that the default choice is good enough that most people never need to make a different one – and the door out is never locked for the people who do.
Keyboard First, Mouse Last
Hyprland, the window manager at the heart of Omarchy, is a tiling compositor: windows snap into an automatically managed grid rather than floating loosely on top of each other, and almost every action – opening an app, switching workspaces, resizing a pane, moving focus – has a keyboard shortcut attached to it. The mouse does not disappear, but it stops being the primary tool. Reaching for a trackpad to drag a window into place, or hunting through a Start menu for an application, becomes the exception rather than the rule.
For anyone who spends the day moving between a terminal, an editor, and a browser, this is not a cosmetic preference. Every trip the hand makes from the keyboard to the mouse and back is a small break in concentration, repeated hundreds of times a day. A keyboard-first environment keeps the hands in one place and the mind in flow for longer stretches at a time – the same instinct that has always driven developers toward Vim motions, tmux, and command-line tools over their graphical equivalents.
The mouse is not banned in Omarchy – it is simply no longer the fastest way to get anything done.
Isn't That Just Windows and Apple With Extra Steps?
This is the fair objection, and it deserves a straight answer rather than a dismissal. DHH is, without question, forcing his opinions onto how you set up your environment – the theme, the terminal, the keybindings, the app selection are all his calls, not yours, by default. In that narrow sense, yes, it is opinionated software imposing a worldview, exactly like Windows or macOS.
The difference is what happens after that opinion is imposed. Every Omarchy default lives in a plain shell script or a readable dotfile sitting on top of an otherwise vanilla Arch installation. Disagree with the terminal choice, the theme, or a keybinding? Open the file and change it, or delete it entirely, and the rest of the system keeps working. Nothing is compiled into a closed binary, hidden behind a vendor update mechanism, or gated by a hardware check you cannot inspect. DHH's opinions are a starting point offered in the open; Windows and Apple's opinions are policies enforced by a system you are not permitted to see inside.
Opinionated Lock-In vs. Opinionated Convenience
- Telemetry you cannot fully disable, feeding data back to a vendor's own data centers
- Hardware gating – TPM 2.0 checks, arbitrary CPU generation cutoffs – that can brick a perfectly capable machine
- Defaults enforced by a vendor update that can change behaviour overnight, with no changelog you can read line by line
- No real way to see what a “recommended” setting is actually doing under the hood
- Every Omarchy default is a plain-text script or config file you can open and read in seconds
- Nothing about the underlying Arch layer is hidden or hardware-gated
- Updates are rolling and transparent, driven by an open project rather than a closed vendor roadmap
- The default is a starting point you are free to override, not a cage you are locked inside
When Arch Breaks, Let the Agent Fix It
Arch Linux has a well-earned reputation for occasionally breaking in ways that intimidate newcomers – a driver update that conflicts with a config file, a package that renames itself, a boot process that suddenly stalls. This is the second half of why the AI moment and the Linux moment are arriving together rather than by coincidence. Because Omarchy's configuration is plain text from top to bottom – shell scripts, dotfiles, systemd units, all readable – an AI coding agent like Claude Code can actually open the relevant file, read the actual error, and propose or apply a real fix. That is a fundamentally different proposition from asking an AI to guess at what is wrong inside a closed Windows registry or a macOS system extension it cannot inspect.
Omarchy leans into this rather than treating it as an afterthought, shipping with AI-assisted developer tooling as part of its default toolchain rather than something bolted on later. It is a small preview of a larger shift: AI is not only changing how software gets written, it is starting to change how the operating system underneath that software gets maintained – and an open, text-based system gives an AI agent something real to work with when the alternative is a black box.
Thousands of Hours, Handed to You for Free
By DHH's own telling, Omarchy is not a weekend project. It is the accumulated result of years of his own personal tinkering with window managers, themes, keybindings, and terminal workflows – by some accounts several thousand hours of trial, error, and refinement – distilled into a single script that reproduces that outcome for anyone else in about a minute. And because Arch is a rolling-release distribution, Omarchy is not a one-time snapshot: the underlying system keeps receiving updates, and DHH continues to refine the opinionated layer on top of it, rather than leaving version one to quietly rot the way an abandoned config repository would.
Your Hardware, Your Rules
There is a quieter benefit sitting underneath all of this: freedom from artificial hardware restrictions. Arch – and by extension Omarchy – does not care whether a machine has a TPM 2.0 chip, does not enforce an arbitrary CPU generation cutoff, and does not demand a minimum amount of RAM to feel dignified rather than degraded. A machine that Windows 11 refuses to touch, or that macOS has quietly stopped receiving updates for, can still run Omarchy comfortably. Paired with a rolling-release model that is not funnelling usage data back to a vendor's data centers by default, the result is a machine that genuinely feels like it belongs to the person sitting in front of it – not to the company that happened to sell it.
The destination Omarchy is aiming at is not really “Arch Linux is better than Windows.” It is the far simpler idea that a computer should feel like it is yours – fast to start, transparent about what it is doing, and configurable by the person actually using it. Whether that machine was bought as a Mac, a Windows laptop, or bare hardware with nothing installed at all, about a minute and one opinionated script is now the distance between it and an environment years in the making.
Further Reading
This article draws on DHH's own public writing about opinionated software, the Rails doctrine, and the Omarchy and Hyprland projects themselves.