j3s argues that Omarchy ships no kernel patches, no package repository, no installer of its own, no security team, and no release cadence — it is fundamentally a shell script that runs pacman and drops in curated dotfiles on top of stock Arch. Calling it a distro creates a false impression of independent engineering effort and, if the term applies to everything, it stops doing useful work.
The editorial extends j3s's argument by framing it as a trust-boundary problem: real distros like Debian come with a 1,000-person volunteer org, a security team, and decades of release engineering, while Omarchy users are implicitly trusting DHH's taste plus the entire Arch and AUR supply chains with only one of those three having a real security response process.
One faction in the HN thread defends Omarchy as a perfectly fine starting point for users who don't want to spend a weekend configuring ~/.config by hand. From their perspective the value is the curated experience and lowered barrier to entry, and the pedantic vocabulary fight misses why people actually adopt it.
Another faction in the thread argues that branding Omarchy as a distro implies independent engineering effort that simply does not exist behind it. Their concern is practical, not pedantic: users misled by the label may not realize that security, stability, and upstream breakage are entirely on Arch and the AUR, not on DHH or Omarchy.
A post titled *Your dotfiles are not a distro* hit Hacker News this week and pulled 134 points before lunch. The author, writing at abyss.fish, takes direct aim at Omarchy — David Heinemeier Hansson's opinionated Arch Linux + Hyprland configuration that DHH has been marketing as a 'distribution' since launching it last year. The argument is short and unsentimental: Omarchy ships no kernel patches, no package repository, no installer of its own, no security team, and no release cadence — it is a shell script that runs `pacman` and drops in a curated set of dotfiles on top of a stock Arch system.
The post lands at a moment when 'distro' has been quietly losing its meaning. Bazzite, Nobara, CachyOS, and a dozen other 'distros' are increasingly thin reskins of Fedora Atomic or Arch with preselected packages and theming. Omarchy is the most prominent example because DHH brought a 37signals-sized megaphone to it. The abyss.fish piece is less a takedown of DHH personally than a refusal to let the vocabulary slip: if everything is a distro, the word stops doing useful work.
The HN thread is, predictably, split. One faction defends Omarchy as a perfectly fine starting point for people who don't want to spend a weekend in `~/.config`. The other faction points out — correctly — that calling it a distro creates a false impression of independent engineering effort behind it.
The semantic argument is the surface. The substantive argument is about trust boundaries and who you're depending on when something breaks. When you install Debian, you're trusting a 1,000-person volunteer organization with a security team, a stable-release manager, and 30 years of release engineering practice. When you install Omarchy, you're trusting DHH's taste plus the entire Arch supply chain plus whatever AUR packages the installer pulls — and exactly one of those three actually has a security response process.
This is not theoretical. Arch's rolling-release model means a `pacman -Syu` two months after install can break in ways the original 'distro' author never tested. Omarchy's installer pins nothing meaningful; you inherit Arch's update treadmill plus a layer of dotfiles that may or may not survive the next Hyprland breaking change. The 'distro' framing obscures that you are, functionally, running Arch with someone else's `~/.config` and a Brewfile-equivalent of `pacman -S` calls.
Compare this to how the term used to be policed. Linux Mint forked Ubuntu's package archive and ran its own update server. elementary OS built Pantheon from scratch and maintains its own SDK. Pop!_OS ships a custom installer, a custom session, and increasingly a custom shell (Cosmic). These are debatable as distros at the margin, but they at least involve engineering output that doesn't exist upstream. Omarchy involves curation — which is valuable! — but curation is what package managers, AUR helpers, and dotfile repos already do.
The community reaction is also a tell about who the audience really is. The defenders of Omarchy-as-distro are mostly people for whom 'distro' means 'a thing I install once and stop thinking about,' which is exactly the audience least equipped to debug what happens when the curation layer and the underlying rolling release disagree. That's the gap the abyss.fish post is poking at. Calling it a distro implies a level of insulation from the messy bits of Arch that simply isn't there.
There's also a precedent worth naming: Manjaro, which *did* run its own package mirrors and held packages back from Arch by a couple of weeks, has spent a decade as a cautionary tale about what happens when a downstream layer pretends to provide stability it doesn't actually engineer. AUR package authors regularly file bugs marked 'not our problem if you're on Manjaro.' Omarchy is a thinner abstraction than Manjaro and inherits a steeper version of the same problem.
If you're running Omarchy or thinking about it, the practical guidance is straightforward: treat it as a dotfiles repo with an installer, because that's what it is. Read the install script. Pin the Arch packages you actually care about. Don't expect DHH to ship a CVE response when the next `xz`-style backdoor lands in a transitive AUR dep. The security boundary you're trusting is Arch's, not Omarchy's, and Arch's is — by design — thinner than Debian's or Fedora's.
For teams evaluating 'opinionated Linux setups' for developer workstations, the abyss.fish post is a useful filter. Ask the maintainer: do you run a package repository? Do you have a security contact? Do you pin or test updates before they reach users? If the answer to all three is no, you're looking at a config bundle, and it should be priced accordingly — useful as a starting point, dangerous as a long-term dependency.
And if you're shipping your own setup as a 'distro' — Bluefin, Aurora, the long tail of NixOS-flake-based 'distros,' your own GitHub repo — this is the moment to ask whether the word is doing honest work for you or borrowing credibility from the projects that actually earned the label.
The Omarchy debate is going to keep recurring because the underlying trend isn't reversing: declarative, scriptable Linux makes it trivially easy to ship a 'distro' that is mostly curation. The honest framing — 'opinionated config bundle on top of $UPSTREAM' — is less marketable than 'distro,' which is why nobody uses it. But the more the word stretches, the less it tells a developer about what they're actually installing, and the more the real distros — the ones with bug trackers, security teams, and release engineering — get conflated with weekend projects that share a GitHub README format. The abyss.fish post is a small act of vocabulary maintenance. It deserves to win.
Top 10 dev stories every morning at 8am UTC. AI-curated. Retro terminal HTML email.