Haiku OS: The Open Source BeOS You Can Daily Drive in 2024

Original Article ↗ Hacker News Discussion ↗

Enthusiasts revisit Haiku OS, an open-source reimplementation of BeOS, weighing its elegant, old-school desktop design and cohesive architecture against the realities of using it as a primary operating system in 2024. Commenters praise its speed, simplicity, strong filesystem metadata model, and growing support for tools like Emacs, Wine, and modern browsers, but point to major gaps such as limited hardware acceleration, lack of full-disk encryption, sparse native applications, and weaker hardware support. Many see it as a promising, distraction-free hobby or niche system rather than a practical replacement for mainstream Linux, Windows, or macOS on everyday machines.

UI and Design Aesthetics

  • Strong divide on looks: some find Haiku’s BeOS-style UI dated, others see it as far more usable and visually appealing than modern flat/macOS/Windows/KDE designs.
  • Many praise 90s-style interfaces (Windows 95–2000, classic Mac, BeOS) for clarity: buttons look like buttons, thick scrollbars, obvious draggable areas, explicit shading/borders, high information density.
  • Modern UIs are criticized for: wasted space, hidden controls, flat/low-contrast designs, hard-to-see active windows, narrow or auto-hiding scrollbars.
  • There is mention of “nostalgic” or retro aesthetics (vaporwave, Frutiger Aero) and themes/projects that recreate classic Windows 95-style looks.
  • Haiku has a “flat” decorator/theme for a more contemporary appearance.

Daily Driver Viability

  • Several commenters state Haiku is not realistically a daily driver, despite the article’s implication.
  • Others argue it can be, if needs are limited to web, email, and a few tools (e.g., Emacs, a decent browser).
  • Reported blockers for daily use:
    • Lack of full‑disk encryption.
    • Historically weak browser situation (partially improved via Falkon).
    • Missing key applications or equivalents.
    • Stability issues on some hardware (e.g., specific laptops, occasional hangs).

Security Model and Multiuser

  • Haiku is largely a single‑user OS; earlier BeOS era felt effectively “run as root”.
  • Some see limited benefit of strict multiuser/root separation on a single‑user machine; others insist password‑gated privilege escalation still matters.
  • Developers are reportedly working on multiuser support.
  • Absence of full‑disk encryption is a hard stop for some, especially post‑Snowden.

Hardware Support, Graphics, and Performance

  • Haiku is x86/x64 only; on Apple Silicon it must run via emulation (e.g., UTM).
  • 3D acceleration is described as essentially missing: only one experimental, out‑of‑tree Radeon driver exists and is hard to set up.
  • Lack of GPU acceleration is a major concern for gaming, modern web, video workloads, and high‑resolution desktops; others downplay it if needs are modest.
  • Some expect Haiku to feel faster and less “crufty” than Linux desktops; others report it didn’t feel significantly faster in practice and sometimes hangs.

Filesystem, Metadata, and Platform Coherence

  • BeFS and Haiku’s filesystem are praised for first‑class indexed attributes:
    • Arbitrary metadata stored as attributes on files.
    • File manager can display and query any attribute as a column, with instant search.
    • Email and media metadata are cleanly modeled this way.
  • This tight integration differs from separate indexers like Spotlight and is seen as a core strength.
  • Some suggest modern filesystems (e.g., ZFS) could gain similar metadata; others defend BeFS as “its own awesome thing.”
  • Haiku is repeatedly lauded as a coherent, tightly integrated desktop OS, in contrast to Linux’s many loosely coordinated distros.

Software Ecosystem and Compatibility

  • Ported Linux/Qt/KDE apps and a Wine port significantly expand available software.
  • There’s tension: once you rely on ported Linux apps, Haiku’s distinctiveness is seen by some as diminished.
  • Support for Emacs and Vulkan is specifically cited as making Haiku more attractive.
  • Package management uses a package daemon with special control over install paths; there is no sudo/su in the traditional Unix sense.

Target Users, Use Cases, and “Distraction‑Free” Appeal

  • One view: Haiku is ideal for simple, single‑user setups (e.g., older laptops, “retirees” who just need mail and web, or a hypothetical kitchen/household appliance‑style PC).
  • Another view: real retirees and mass‑market seniors are more likely to use mainstream platforms; the niche of tech‑savvy older users is small.
  • Haiku is suggested as an appealing “distraction‑free” environment: few zero‑day exploits, less modern web cruft, and fewer attention‑grabbing apps.

BeOS Legacy, Nostalgia, and Philosophy

  • Multiple commenters fondly recall BeOS as their main OS in the late 90s/early 2000s: fast boot, responsive UI, but limited apps.
  • Some lament BeOS’s failure in the “kitchen computer” market, contrasting it with the later success of the iPad.
  • Haiku’s mission is described as recreating a fully‑fledged, general‑purpose desktop OS in the BeOS spirit.
  • There is concern that widespread adoption would inevitably erode Haiku’s current conceptual purity and coherence, as happened with other platforms.

Unclear or Open Issues

  • Long‑term plans for robust, in‑tree GPU acceleration are uncertain; it’s acknowledged as “difficult” and not a top immediate priority.
  • It’s unclear how well Haiku’s security model will evolve once multiuser and FDE are implemented, and how that will affect its simplicity.