Did you know the most talked-about desktop of 2026 ships with a retro Winamp-style music player and no apology for it? The Omarchy manual calls the project an “omakase Linux distribution”: Arch Linux underneath, the tiling window manager Hyprland on top, the desktop construction kit Quickshell holding the panels together, and a chef’s selection of Neovim, Chromium, Obsidian, LibreOffice, Kdenlive and OBS Studio already on the plate. Its author is David Heinemeier Hansson (DHH), creator of Ruby on Rails and co-owner of 37signals. The manual speaks in his first person: this is the machine he works on, served whole.

What changed in 2026 is the backing. Per the Omacom Foundation announcement, twelve Founding Patrons pledged $1 million each. Three Founding Corporate Patrons, among them DigitalOcean and Alibaba Cloud, committed $1 million a year for three years or $1.5 million in tokens; Alibaba Cloud signed on as recently as 22 September. More than 800 donors added over $120,000 through open patronage, bringing the total to roughly $21.7 million. The Register had counted $18.5 million on 17 September, and the figure kept climbing. The nonprofit will hold the trademarks and, in its own words, “support the open-source projects and developers Omarchy depends on.”

That last clause matters most. Omarchy is a curation, and the people carrying the load underneath rarely get seen: the Arch maintainers who keep a rolling repository coherent, Vaxry and the Hyprland contributors, the Quickshell developers, and the Arch Wiki editors whose pages have quietly repaired more laptops than any vendor hotline. Packaging all of that so a newcomer boots into a themed, keyboard-driven desk on day one is engineering in its own right, and often the harder half. How-To Geek’s reviewer spent seven days with it and came away understanding why it is the most discussed Linux project of the moment.

←TODAY: A Linux desktop that began as one developer’s own setup now has a nonprofit holding roughly $21.7 million in pledges.
→3012: Zurich 3012 still opens its 2026 IFC files, because the format and the system reading it both stayed open.
Fulcrum: Funding keeps a desktop alive for years; an open format keeps a building’s model readable for generations.

What lands on a Zürich desk

First, the honest part. Archicad and Rhino 8 do not ship native Linux builds, so Omarchy won’t become the production seat in a 12-person studio. Your Rhino licences (PAZ Academy resells them) and the Grasshopper 2 definitions PAZ has taught since the Alpha stay on Windows or macOS. What Linux runs natively is the open IFC chain: IfcOpenShell, Blender with Bonsai, Python, git, and LibreOffice for the Baubeschrieb.

IFC is not compiled. It is plain text, and you can read it in Omarchy’s Neovim. A wall in an IFC4 file looks like this: #42=IFCWALL('2O2Fr$t4X7Zf8NOew3FLOH',#5,'Wall-001',$,$,#38,#40,$,.STANDARD.); Read it left to right. #42 is the instance id and IFCWALL is the class. The 22-character string is its GlobalId, #5 points to the owner history and 'Wall-001' is the name. Each bare $ is an attribute left empty (description, object type, tag). #38 and #40 point to placement and geometry, and .STANDARD. is the predefined type. Nine attributes on one line, no licence server involved.

The trade-off is built into the system: Arch is a rolling release, so the newest Blender arrives fast, and a breaking update can arrive just as fast on the morning of a Wettbewerb deadline. Yes, you will edit a config file. Nobody has died of it.

From where I sit in the late 2070s, the buildings that aged worst were not the ugly ones. They were the ones whose models nobody could open once a vendor went dark. When you pick a stack, ask one question: if the vendor disappears, can a 25-year-old still read the file?

The Tool: Omarchy, DHH’s opinionated Arch Linux desktop, documented in the manual at omarchy.org. It earns a computational designer’s afternoon by turning a spare laptop into a tiling workstation: terminal, Blender and the engineer’s PDF comments side by side, none hiding behind another. The project now runs a team per hardware platform, Omarchy M for Apple machines and, per the Omarchy news page, Omarchy Dragon for Qualcomm Snapdragon laptops.

Setup: follow the manual’s installation chapter on a spare machine, then open a terminal with Super + Return and add the open IFC toolchain.

# fresh Omarchy install (Arch underneath)
sudo pacman -Syu --needed python git blender
# Arch protects the system Python: use a venv
python -m venv ~/ifc-lab
source ~/ifc-lab/bin/activate
pip install ifcopenshell
mkdir -p ~/ifc-lab/models
# proof of life: prints the IfcOpenShell version
python -c "import ifcopenshell; print(ifcopenshell.version)"

First steps:

1. Press Super + Space for the launcher and skim the manual’s hotkeys. The one habit: each new window takes a slice of the screen instead of floating on top.
2. Save one IFC export from a live project as ~/ifc-lab/models/model.ifc, open it in nvim, search for IFCWALL and read a line against the breakdown above.
3. In Blender, go to Edit → Preferences → Get Extensions, install Bonsai, open the same file and let Hyprland tile it beside the terminal.
4. Save the Hack script below as ~/ifc-lab/check_walls.py and, with the venv active, run python check_walls.py from that folder. Fix what it flags on the Archicad seat, re-export, repeat until it prints nothing.

Atelier: For a Zürich studio working with AI-assisted massing and automated exports, the bottleneck has moved from drawing to checking what leaves the office. A Linux box that reads plain-text IFC is a cheap, auditable checkpoint that no licence renewal can switch off. Monday move: install Omarchy on the oldest laptop in the cupboard and route one live project’s IFC export through it before the file goes to the structural engineer.

Hack: Catch every wall that is about to leave the office without its common property set, before the engineer in Bern catches it for you.

import ifcopenshell, ifcopenshell.util.element as E
model = ifcopenshell.open("models/model.ifc")
for wall in model.by_type("IfcWall"):
    if "Pset_WallCommon" not in E.get_psets(wall):
        print(wall.GlobalId, wall.Name)

Each printed line is a wall missing the standard FireRating, LoadBearing and IsExternal fields that the Bauleitung and the thermal consultant check first. Swap IfcWall for IfcSlab and Pset_SlabCommon to audit floors.

Learn-it:

• The Omarchy manual: installation and basics; read it before you touch the USB stick.
• Introducing Omarchy Dragon: the Snapdragon port, for offices on ARM laptops.
• Omacom Foundation announcement: who funds the project and what for.
• How-To Geek: seven days with Omarchy: a newcomer’s first week.
• PAZ note: the Linux box is the checkpoint, not the authoring seat. Archicad and Grasshopper work stays where the PAZ Grasshopper↔Archicad Library runs.

Pick one project, one IFC export and one spare laptop. Run the five lines, count the walls that print, and bring that number to your next coordination meeting.