The AerynOS Developer… Has Gone to the Toilet

Overview

The video is framed as a “breaking news” joke about whether a developer washed his hands. Underneath the humor, however, it delivers a serious critique of how Linux-focused outlets choose which distribution stories to cover—arguing that coverage is repetitive and biased toward familiar names.

---

1) Clarifying the target and the tech merit

The speaker clarifies that they have nothing against AerynOS (the video’s main example), describing it as a serious alpha project with real technical value, including:

• A custom Moss package manager
• Atomic updates, intended to prevent systems from ending in a half-upgraded state

They also credit the project’s founder, Ike Doherty, as technically capable—noting he created Solus and Budgie.

Continuity beyond a single figure

The speaker emphasizes that Doherty is no longer leading AerynOS:

• He left Solus in 2018
• He stepped down from AerynOS in April 2025
• The project later reported difficulty contacting him, and development continued under Rune Morling

From there, the speaker pivots into a moral/organizational argument: developers should not be treated as indispensable “holy” figures. Long-term project continuity depends on:

• documentation
• delegation
• communication
• shared infrastructure

Because real life and careers change.

---

2) The main complaint: disproportionate editorial attention

The speaker asks why SerpentOS/AerynOS keeps appearing in their news feed and in articles from outlets such as Phoronix and Linuxiac.

They present a quantitative-ish comparison:

• Jan 2025 to early Oct 2026:
  • 18 feature articles on Phoronix
  • 19 on Linuxiac
    • including coverage under a previous name (“Serpent OS”)
• Total: 37 articles across ~21 months, averaging about monthly coverage on each site

Why the coverage is criticized as “not really news”

They argue that much of this content barely functions as “news.” Instead, it often repeats incremental update announcements such as:

• GNOME/Plasma/kernel/cosmic updates
• installer or image preparation
• occasional logo changes

---

3) Why this coverage pattern is criticized

The speaker argues specialized journalism should prioritize:

• original work
• the significance of the problem
• impact on users
• quality of the solution
• comparisons and research (not merely release bumps)

They also argue that if a publication covers one distribution’s routine updates, it should apply the same standard to others that also:

• regularly update packages
• improve installers
• add desktops
• fix issues

Visibility mistaken for importance

They claim the net effect is that visibility becomes mistaken for technical importance:

• familiar projects are easier to write about
• familiarity increases coverage
• more coverage reinforces perceived importance
• the audience then assumes less-covered projects are less valuable—when they may simply be less well known

---

4) Proposed remedy: broaden the spotlight

The speaker suggests that outlets should introduce unfamiliar distributions more often (e.g., monthly or every few months), focusing on learning:

• what the distribution does
• what’s missing
• why it matters

They provide example projects that could be explored instead of repeating the usual names:

• Guix (declarative configuration, transactional rollbacks)
• Chimera Linux (Linux kernel + core FreeBSD tools; musl/LLVM; Dinit)
• Secure Blue (Fedora Atomic with additional security measures)

They also criticize a tendency to see the same mainstream distributions repeatedly (e.g., Debian, Ubuntu, Arch) across multiple outlets—described as “sentences rearranged.”

---

5) Additional evidence: headline dominance and an upcoming analysis

The speaker says they did more than go by impression. In a larger upcoming video, they plan to show a broader headline sample from the last two years.

In a small sample, they report:

• Debian + Ubuntu + Arch account for over 50% of titles
• adding seven more distributions pushes combined share beyond 80%
  • with EndeavourOS among the frequently present

Their conclusion: the editorial mechanism likely rewards recognizable names, not necessarily the most impactful engineering.

---

6) Continuity as the deeper theme (including media)

The video ends by generalizing continuity beyond software:

• continuity applies to creators and to media topics as well
• the speaker claims they choose topics based on preference, but argues the audience/press has the right to question those choices

Final metaphor

If a developer has to “go to the bathroom,” the press shouldn’t hover at the door. Instead, outlets should cover the broader ecosystem and avoid conflating “always being visible” with “always being central.”

---

Presenters / Contributors

• Ike Doherty (founder mentioned)
• Rune Morling (named as current leadership)
• The speaker/host (unnamed in subtitles; also preparing additional videos)
• Outlets referenced: Phoronix and Linuxiac (no individual authors named in the subtitles)