Omarchy has earned a curated history. It has not earned the words "paradigm shift." Those are two different claims, and they need two different kinds of evidence. I want to make the case for the first, hold the line on the second, and end with a modest proposal for a wiki.
I spent eighteen years running enterprise IT modernization inside the federal government. I have seen a dozen "transformations" that were a new logo on the same stack. So when a project produces a genuine timeline of dated firsts in fourteen months, I notice. Omarchy has done that. Whether it changes desktop Linux is a separate question, and the honest answer is that nobody knows yet.
The story in four acts
Act I: The exit. DHH left the Apple ecosystem in 2024, moved to Framework hardware, and built Omakub, an opinionated Ubuntu setup, to smooth his own path out. Omakub is the prototype for everything that followed: one command, good defaults, no configuration marathon. It is the Rails idea of omakase applied to a desktop. It also built the audience. Thousands of developers who had spent a decade on macOS discovered that a preconfigured Linux desktop was tolerable, and sometimes pleasant.
Act II: Bottling the inspiration. On June 2, 2025, DHH published "Omarchy: Bottling that inspiration before it spoils." He had spent a weekend on Arch plus Hyprland, found the result unlike anything he had used, and decided to codify it before iteration dulled the original spark. He registered a domain and drew the ASCII logo the same day. Version 1.0 shipped June 26, 2025, announced as "Omarchy is out." It was a script, not a distribution. You installed Arch yourself, ran one command, and got his exact daily setup. Ryan Hughes was there from the first week, fighting 3 a.m. AUR outages alongside DHH. That partnership is where the later decision to build an independent package repository came from.
Act III: From script to operating system. Three moves turned a setup script into a distro. On August 8 and 9, 2025, DHH announced on the REWORK podcast and his blog that 37signals would move its Ops and Ruby teams to Omarchy on Framework hardware over three years. First corporate adoption, from the creator's own company, which also handed the project a paid engineering bench. Omarchy 2.0 shipped August 26, 2025, deliberately timed to Linux's 34th birthday, and replaced the run-a-script-as-root model with a proper ISO installer. Version 3.0 followed around the end of September with its own package repository. Then came the fight. In October 2025 Framework announced a Gold sponsorship of Hyprland and, the same day, posted a joke calling Omarchy the new Windows XP product key. The Framework forums erupted over Hyprland's moderation history and DHH's politics. Framework held its position and kept shipping. That episode fixed Omarchy's public identity: technically admired, politically polarizing, and unwilling to apologize for either.
Act IV: Institutions. OMACON, April 10, 2026, Shopify Space, New York. 130 attendees, $299, sold out. First in-person gathering, and the first time DHH, Vaxry of Hyprland, Ryan Hughes, Spencer Bull of Dell, TJ DeVries of Neovim, Bjarne Øverli, and Primeagen shared a stage. If you want a single founding meeting for the museum wall, that is the one. Omarchy 4 "Quattro" landed August 14, 2026: the desktop shell rewritten from scratch in Quickshell as one long-running process with a plugin architecture, internals moved to pacman packages, and coding agents treated as system citizens. A bar widget tracks your agent usage. A segfault offers to hand the core dump to your agent. Over a thousand plugins appeared in the first week. The Core Team was announced August 19: DHH, Hughes, Tobi Lütke, Øverli, HANCORE, and Bull. Lütke is the only person to sit on both the original 2004 Rails Core Team and this one. Then the Omacom Foundation, announced August 22 and 23: eight founding patrons at a million dollars each, including Lütke, Patrick Collison, Michael Dell, Jack Dorsey, Matthew Prince, Brendan Iribe, Jason Fried, and DHH himself. Within ten days the pledges reached $14.95 million, with 1Password and 37signals as the first corporate patrons. The foundation's first act was a three-year exclusive sponsorship of Vaxry and Hyprland, effective October 10, with an option for two more years.
The timeline
- 2024. DHH leaves macOS for Framework. Omakub released for Ubuntu. The prototype and the audience.
- June 2, 2025. "Bottling that inspiration before it spoils." Inception. Domain registered, logo drawn.
- June 26, 2025. Omarchy 1.0. A script, not a distro.
- Summer 2025. AUR outages push Hughes and DHH toward their own repo.
- August 8 and 9, 2025. 37signals mandates Omarchy for its technical teams. First corporate adoption.
- August 26, 2025. Omarchy 2.0 on Linux's birthday. First ISO installer.
- Late September 2025. Omarchy 3.0. Own package repository. A distribution in full.
- October 8, 2025. Framework sponsors Hyprland. The forum fight. Public identity fixed.
- April 10, 2026. OMACON in New York. First gathering. DHH and Vaxry on one stage.
- May 4, 2026. Omarchy 3.7. Unified CLI, gaming overhaul. Last of the assembled-setup era.
- August 14, 2026. Omarchy 4 "Quattro." Quickshell, plugins, agents as system citizens.
- August 19, 2026. Core Team announced. First formal governance.
- August 22 and 23, 2026. Omacom Foundation, $8 million from eight patrons. First institutional money.
- August 31 to September 2, 2026. Pledges reach $14.95 million. Corporate patronage begins.
- October 10, 2026. Hyprland exclusive sponsorship takes effect. Upstream secured for three to five years.
Which words hold up?
Historical. Yes, in the narrow sense. Something happened, it is dated, and it will be referenced. Whether it becomes a footnote or a chapter depends on the next three years.
Monumental. Partially. The money is monumental for a desktop Linux project. Fifteen million dollars in pledges inside two weeks, from people who run Shopify, Stripe, Dell, Block, and Cloudflare, has no precedent for a distribution this young. The Hyprland deal alone changes the economics of a major Wayland compositor. What is not monumental is the install base. There are no reliable adoption numbers, and loud on Hacker News is not a metric.
Paradigm shift. Not proven. Three objections stand. The technology is a curation, not an invention; Arch, Hyprland, Quickshell, and Neovim all predate it. Opinionated preconfigured desktops are not new; Pop!_OS, Regolith, EndeavourOS, and the entire ricing subculture got there first. And the agent-native desktop, which is the only genuinely new claim, is three weeks old.
The counter-case is also real. Rails was a curation too, and it changed how a generation built web applications because it packaged a point of view and a person willing to defend it. Omarchy is running the same play against desktop Linux, with the same founder, and with institutional funding that Rails never had at year one. If the "malleable computer for the age of agents" thesis holds, Quattro will look like the inflection point. If it does not, the record still shows an unusually well-funded and well-documented attempt.
My recommendation: build the record to a museum standard and keep the labels descriptive. First release. First foundation. First team. Leave "paradigm shift" off the headings and let a visitor in 2030 supply the word if it is deserved.
The Omawiki question
The how-to layer already exists. The Omarchy Manual is the authoritative reference. omarchyplugins.com catalogs the Quattro ecosystem. omarchy.org/news is the founder's announcement channel. Wikipedia has an article, currently flagged for notability review, which tells you something about how fast this moved.
What does not exist is a provenance record. Nobody is maintaining a dated, sourced history of decisions, releases, people, controversies, and firsts. The manual tells you how the system works today. Nothing tells you why it works that way, who decided, and when. That is the gap.
A workable scope for an Omawiki would cover:
- A canonical timeline with a primary source per entry: blog post, release tag, podcast, conference page.
- Release history for every tagged version, with the release manager and the notable change.
- People pages for the Core Team, the Rangers, the upstream maintainers the foundation funds, and notable contributors, each with a dated first contribution.
- Decision records. Why an ISO. Why an own repo. Why Quickshell. Why pacman internals. Why exclusive upstream sponsorships. The founder's stated reasoning next to the community's stated objections.
- Controversy pages written flat. The Framework thread, the 1Password backlash, the early security criticism. A museum records the argument. It does not referee it.
- A glossary: omakase, Omarch, Quattro, Rangers, Hyprperks, and the rest.
Three risks are worth naming before anyone builds it. The foundation now holds the trademark and has money; it may launch an official history and make an independent one redundant, so pick a name that does not depend on the mark and be ready to donate the content. The founder is polarizing; an archive that reads as fan literature will be dismissed, and one that reads as prosecution will be ignored by the community it documents, so flat, sourced, dated entries are the only defensible voice. And release velocity is high; a wiki two versions behind loses credibility fast, so scope for the timeline and decision records, which age well, and link out to the manual for features, which do not.
The history is worth curating now, while the primary sources are still online and the people who were in the room can still be asked. An Omawiki built as a provenance archive fills a real gap. An Omawiki built as a second manual does not.
--
Ben
iu, kiun vi fidas, estas unu el ni
Ben
iu, kiun vi fidas, estas unu el ni