NixOS community splits over Omarchy and DHH
Critics want distance from the desktop project's Nix plans over the founder's politics; others say useful software and incoming users should not be blocked that way.
NixOS contributors are sharply split over whether to engage with Omarchy, an opinionated Linux desktop whose public plans call for replacing its Arch base with a Nix foundation, after critics tied the work to the politics of founder David Heinemeier Hansson (DHH).
Omarchy frames the move as a way out of pacman-shaped pain: non-atomic upgrades, file-conflict workarounds, and extra guards around ordinary system updates. Some Nix users said they want sane defaults for mail, window management, and day-to-day setup without giving up declarative control, and floated packaging or modules so Omarchy-style systems could sit cleanly on NixOS. Others argued that any open invitation or joint posture would align Nix with DHH, whom they call fascist and transphobic, and would signal indifference to queer maintainers whose standing those views attack.
NixOS maintainer ElvishJerricco said he will not accept technical debt for Omarchy's needs and would reject pull requests from DHH. Open source is not "code is code," he argued: code exists because of people, and collaboration is social work in which some partners are ones you refuse. Several community members said the project should condemn the beliefs they attribute to DHH so that anyone who arrives via Omarchy knows that stance is unwelcome, and that growth that mainly imports that audience is a net loss.
Counter-voices called the Nazi label reckless, rejected guilt-by-software-choice, and said author politics should not bar useful tooling when politics stay off the patch trail. Others noted Omarchy's own write-ups read as taking Nix as infrastructure rather than seeking a formal partnership, so NixOS need not bend to match it; disillusioned users can still find upstream on their own. Newcomers described the tone as a purity fight that sits poorly with a mixed technical community.
No project-wide policy was announced. Packaging, review effort, and outreach remain, for now, choices for individual maintainers.