DHH Responds to Omarchy's Critics (Including Me)

Overview

This is a podcast/interview where the host—previously known for critical videos about the Omarchy/Omachi project—says Omachi is now too significant to ignore. The host invites Omachi creator David Hiner Hansen (“DHH”) to explain what he’s building, why, and how it’s progressing, with security receiving special emphasis.

---

What’s happening with Omachi right now

• Expansion into many sub-projects

  • DHH says Omachi has grown into numerous “sub-projects,” to the point that he’s working roughly 16 hours/day.

• Core pitch: art/design + usability + serious engineering

  • The project combines art/design and usability with serious engineering, including:
    • custom kernels,
    • performance work,
    • and especially security.

• Plugin ecosystem and “mutability”

  • The interview highlights the Omachi Quattro / Agenda OS era as enabling people to mutate the system through a large plugin ecosystem.

• Fast community creation

  • DHH claims that in the first few weeks, thousands of plugins were created.
  • He frames this as “vibe coding,” though he notes the phrase should probably be retired.

---

DHH’s motivation: “building the perfect computer” and evangelization

• Not primarily money

  • DHH claims money is no longer the main driver; the main driver is a long-standing love of computers since childhood.

• How he got into Linux

  • He describes moving away from Mac:
    • Apple felt increasingly focused on control (including distribution “tolls” and business pressure such as the Hey.com revenue dispute).
  • His early Linux experience:
    • Tried Ubuntu and found it too “Duplo.”
  • Then he shifted toward configurability:
    • tiling window managers,
    • Hyperland/Arch-style workflows,
    • which he compares to “Lego,” unlocking his desire to build a personal ideal.

• An evangelization mindset

  • He likens Omachi’s purpose to Ruby on Rails: once he believes there’s a better approach, he feels it’s selfish not to share it.

• Why now (timing alignment)

  • DHH argues several things finally line up:
    • tiling window manager maturity (e.g., Hyperland),
    • better Linux-capable hardware (notably new laptop/chip ecosystems and Intel platforms),
    • and the “agent revolution” (AI coding agents), which can speed up and improve development.
  • He also argues AI agents can reduce typical Linux friction—broken systems can often be repaired by AI rather than forcing users into hostile, forum-driven troubleshooting cultures.

---

Response to “drama” and critics

• The host notes Omachi has been surrounded by drama and interpersonal issues in public discourse.
• DHH does not deny controversy exists. Instead, he frames the mission as shifting the community toward:
  • optimism,
  • constructive progress,
  • and a more welcoming “happy about computers” culture.

---

The “agents” thesis and why Linux fits

• Linux as naturally agentic

  • DHH argues Linux is uniquely suited to an agentic operating system because so much of it is scriptable:
    • CLI-driven,
    • config-driven,
    • and therefore automatable and debuggable.

• Contrast with Windows/macOS

  • Windows is criticized as locked down with archaic, cursor-based automation paradigms.
  • Apple is criticized for security/permission models that make “mutation” harder.

• Ecosystem tension

  • He claims some parts of the Linux ecosystem are neutral at best and sometimes hostile to AI/agent workflows.
  • He cites examples of projects that argue AI coding shouldn’t be allowed.

---

Adoption strategy: “escape velocity,” not universal market share

• DHH says the goal isn’t maximum users; it’s reaching “escape velocity”:

  • enough adopters to sustain and grow the project.

• Omachi as an acquired taste

  • He compares it to coffee/champagne/dark chocolate: not everyone will want it, but that doesn’t prevent meaningful adoption.
  • He speculates 20–30% as plausible, referencing Windows 95 as a historic analogy.

• Transferring enthusiasm

  • For broader population growth, he emphasizes transferring enthusiasm.
  • He argues Linux communities can be allergic to marketing/presentation, incorrectly assuming polished messaging implies low technical merit.

---

Next steps DHH outlines

• Community engagement (“retail politics” of evangelism)

  • Direct communication,
  • responding to concerns,
  • and iterating based on feedback.

• Continued fundraising and scaling

  • He states Omachi has raised $20M and wants more.
  • He frames money as an accelerant for:
    • people,
    • partnerships,
    • and hardware/platform alignment.

• Technical product goals

  • Move more of the plugin ecosystem into the core to improve compatibility and out-of-the-box usability.
  • Reduce reliance on wikis for device-specific workarounds (e.g., Wi‑Fi, Bluetooth, RGB, webcam issues).
  • Pursue very broad hardware compatibility:
    • begin with a “vintage” Mac laptop range,
    • then expand to other OEM lines.

• Future-facing capability examples

  • “Voice modes,” where users can speak requests that trigger system/plugin changes.
  • Improved out-of-the-box input methods and regional language support (he mentions Japanese/Chinese/Korean input).

• Development approach

  • He describes development as many parallel tracks managed inside an organizational “base camp” structure.

---

Security: number-one priority, plus hires and responsible disclosure

• Top priority since the Omachi Quattro launch

  • DHH repeatedly emphasizes that security is the #1 priority since launch and a key reason new features haven’t been pushed as quickly.

• Built on a hardened foundation

  • He claims Omachi is built on Linux’s hardened ecosystem rather than “shaky” foundations.

• Dotfiles criticism vs claimed real risk

  • He addresses the allegation that Omachi is “just dotfiles.”
  • He accepts that config/dotfile risks can exist, but stresses core components are standard, battle-tested Linux pieces (e.g., kernel, OpenSSL, etc.).

• Security team and professionalization

  • He describes forming a security team after the core team.
  • He claims hires include:
    • a Linux kernel maintainer involved in kernel hardening and PCI subsystem issues,
    • and a Quickshell security-focused engineer.
  • He says responsible disclosure is handled seriously, including listing researchers/collaborators via a security credits page.

• Responsible vs irresponsible disclosure

  • He distinguishes responsible reporting from “irresponsible” disclosures, including some that found issues upstream-wide.
  • He argues even hostile “hatefinding” can still produce fixes that benefit Linux generally.

---

Clarifying the AUR issue (Arch User Repository)

• The host raises a concern: AUR isn’t vetted/scanned by default (noting roughly 117k packages).
• DHH clarifies:
  • Omachi does not use AUR packages in the default system.
  • AUR is only optional through an interface; users can review builds before installing.
  • Omachi builds and ships its own repository packages, aiming for eventual package sovereignty (no dependency on AUR).
• He rejects heavy warning-popup approaches as ineffective (users learn to click through anyway).
• Instead, he argues the long-term solution is reviewing and controlling the full build/package pipeline.

---

“Kids” vs “adults” security model

• The host worries that a “kids version” that still allows AUR installs could be disastrous and lead to bad publicity from hacks.
• DHH responds:
  • A kids version will exist.
  • It won’t allow pseudo (restricted privileges).
  • Kids won’t be able to install packages on their own.
  • It will include parent-facing safeguards such as:
    • whitelisted DNS/web access,
    • time limits/time nudges.
• He frames adults as responsible for their own machines (“fork and spoon”), while kids require protective constraints and structured onboarding.

---

Overall message of the interview

Omachi is presented as a Linux desktop aimed at reclaiming “computer wonder” by merging:

• polished UX,
• customizable aesthetics,
• and modern AI agent workflows.

The interview also serves as a defense against security and community-drama criticisms, emphasizing:

1. controlled packaging and plans for sovereignty,
2. an active security program with professional hires and disclosure processes,
3. separate safety boundaries for children.

---

Presenters / contributors

• David Hiner Hansen (“DHH”) – Omachi creator/presenter
• Podcast host (unnamed in subtitles) – interviewer/presenter