VitruvianOS – Desktop Linux Inspired by the BeOS

Original Article ↗ Hacker News Discussion ↗

Project goals and architecture

  • VitruvianOS is described as a Linux-based OS that re-implements BeOS/Haiku mechanisms on top of the Linux kernel rather than “just a theme.”
  • Core piece is “Nexus,” a custom Linux kernel subsystem providing BeOS/Haiku-style IPC, node monitoring, device tracking, and messaging.
  • Nexus is framed not as a syscall translation layer but as a native implementation of the same IPC semantics using Linux primitives, making Haiku apps “first-class citizens.”

Relationship to Haiku and Linux

  • One view: Vitruvian is effectively “Haiku on a Linux kernel,” aiming to pair BeOS-like UX with Linux’s broader hardware support and ecosystem.
  • Counter-view: If you like BeOS, you should just run Haiku, which is seen as the “real deal” with the “soul,” while Vitruvian is a compatibility construction.
  • Some confusion remains over how much is a port vs. reimplementation; even interested readers say they are “confused.”

Graphics, apps, and compatibility

  • Vitruvian uses its own windowing system (Haiku app_server–style) and explicitly does not use X11 or Wayland; thus, standard Linux GUI apps don’t run natively.
  • There are hints of future support via xlibe and a Haiku-wayland effort, possibly leveraging real GBM buffers on Vitruvian, but current state is unclear.
  • Some argue that shipping X would just make it “another Linux distro,” undermining the distinct UI vision.

Real-time kernel and performance

  • It currently uses a real-time–patched Linux kernel for low-latency desktop use.
  • Commenters debate whether RT makes a practical difference for desktops; developers say the BeOS-like graphical and media stack is timing-sensitive but admit it might prove unnecessary and is easy to swap out.

UI/UX and usability reactions

  • Strong nostalgia for BeOS-style window “tabs” that can be stacked across apps; Vitruvian is said to run the “real app_server,” so this behavior is expected.
  • BeOS-like aesthetics (3D-ish widgets, yellow title bars, distinctive icons) are widely praised as a welcome break from flat minimalism.
  • Some criticize the marketing copy (“human at the center”) as vague “slop” and note non-standard choices like close buttons without an “X” as potentially non-intuitive.

Nostalgia and historical context

  • Many reminisce about BeOS’s responsiveness, multimedia capabilities, and smooth multitasking on 1990s hardware, often contrasting it with fragile Windows 95/98 and early Linux desktops.
  • Discussion branches into the BeOS/Haiku lineage, prior Linux+BeOS hybrids (BlueEyedOS, Cosmoe), and the broader desire for experimentation beyond Unix-derived desktops.

Concerns, skepticism, and open questions

  • Skeptics worry Vitruvian may combine the downsides of a niche stack (limited applications) with Linux’s complexity.
  • There is debate over language/runtime support (e.g., Ruby, PHP) on Haiku and what that implies for Vitruvian; reports conflict and are unresolved in-thread.
  • Some ask whether this can be a daily-driver given lack of native X/Wayland apps, containers, IDEs, and gaming stacks (e.g., Proton); answers are mostly speculative or “not yet.”
  • Overall sentiment mixes excitement about real technical differentiation with doubts about practicality, maturity, and long-term viability.