Chimera Linux works toward a simplified desktop

Original Article ↗ Hacker News Discussion ↗

Chimera Linux, a new distribution that pairs the Linux kernel with a FreeBSD-style userland, aims to create a “simplified” desktop system by reducing complexity in the low‑level plumbing rather than inventing a new user interface. Commenters contrast its BSD tooling, non‑systemd design and stateless configuration goals with conventional GNU/Linux distros, while noting it still offers mainstream desktops like GNOME and KDE and better hardware support than the BSDs. Reactions range from enthusiasm about its clean architecture and RISC‑V support to concerns over installer usability, lack of built‑in rollback mechanisms, and whether GNOME fits the project’s simplicity narrative.

Architecture & Goals

  • Chimera Linux combines a Linux kernel with a BSD userland (FreeBSD-style tools), aiming for smaller, simpler, more consistent base utilities than GNU coreutils.
  • Linux is chosen over a BSD kernel mainly for broader hardware support (especially Wi‑Fi), better desktop software compatibility, and strong container (OCI) support.
  • The project seeks systemd‑like capabilities while avoiding systemd, via its own modular components such as Turnstile, and targets “stateless” /etc and /var.

Desktop Environment & “Simplified” Debate

  • The “simplified desktop” label is widely questioned. Many note Chimera ships conventional DEs (GNOME, KDE, XFCE, LXQt, etc.), not a new or minimal UI.
  • Some suggest the phrase should be read as “simplified desktop Linux distribution” (internals, not UX).
  • Opinions on GNOME sharply diverge: some find it very simple and ideal for nontechnical or older users; others call it “dumbed down,” missing basic features, and problematic for accessibility.

Packaging, Tooling & Rollbacks

  • Chimera began as a rethink of Void Linux’s packaging; it replaces shell-based templates with Python-based “cports” that build binary packages for apk 3.
  • There is debate over Python’s complexity vs. alternatives like Lua; defenders argue Python’s rich standard library drastically reduces extra dependencies and complexity in the tooling.
  • apk keeps an explicit “world” file of requested packages; reverting that file plus transactional installs gives a primitive form of rollback and reproducibility, but some argue it falls short of NixOS/Guix-style atomic rollbacks and bootable previous generations.

Relation to BSDs and Other Distros

  • Comparisons arise with Debian GNU/kFreeBSD, NixBSD, and OpenBSD/FreeBSD more broadly.
  • Some see Chimera as delivering a BSD-like, integrated, simple userland without BSD’s hardware gaps and compatibility limitations.
  • Others ask “why not just use a BSD?”; responses emphasize Linux drivers and containers, while BSD userland is kept for its simplicity and consistency.

Usability, Hardware & Meta

  • The installer and live ISOs draw criticism as confusing or fragile; some argue implementation simplicity is being prioritized over user-friendliness.
  • Reports note positive hardware behavior (e.g., KDE image working out-of-the-box on an unusual 12" MacBook) and PPC/RISC‑V support, though PPC hardware is seen as niche and expensive.
  • Several commenters value that Chimera avoids glibc, GNU tools, GCC, and systemd, seeing it as “non‑GNU Linux” and culturally distinct from the usual GNU/Linux ecosystem.