Infinite Mac: BeOS

Original Article ↗ Hacker News Discussion ↗

Fans of classic BeOS and its open-source successor Haiku reflect on why these systems still feel fast, elegant, and innovative compared to today’s mainstream desktops. Commenters highlight Haiku’s surprising usability, technical quirks (like its C++ ABI and multithreaded GUI), and obstacles such as hardware support and lack of encryption, while also exploring what might have happened if Apple had acquired Be instead of NeXT. The thread branches into related retro-operating systems, UI ideas like window tabbing, and efforts to revive BeOS-style environments on modern kernels.

Haiku OS and BeOS Today

  • Multiple commenters recommend Haiku, calling it pleasant, surprisingly usable, and now with Firefox and even a draft Nvidia driver.
  • Others report hardware issues: Haiku doesn’t boot on some modern systems and still lacks disk encryption.
  • Haiku policy reportedly rejects AI‑generated code; contributors are expected to understand and explain their work.
  • Binary compatibility constraints from BeOS’s old C++ ABI persist: 32‑bit Haiku builds with an old GCC can run BeOS apps, 64‑bit modern GCC builds cannot.

Modernizing Legacy OSes

  • One project reimplements classic Mac System 6 on bare metal (e.g., Raspberry Pi) with POSIX shell, BusyBox, OpenSSH, USB MIDI/ethernet/audio, targeting old DAW workflows.
  • Debate over targeting System 6 vs 7.x: 7.5.3 is praised for broad compatibility; 6 runs better on very constrained 68k Macs.
  • There’s interest in “modern Linux with Win95/XP shell”; examples include running the XP shell via Wine.
  • Some speculate AI could rapidly generate new app ecosystems for old OSes, and even help improve the OSes themselves.
  • Others argue fully decompiling and modernizing classic Mac OS would likely break app compatibility; high‑level emulation per app is suggested as a better isolation strategy.
  • Conflicting claims about classic Mac OS: one side says it lacked modern preemption/VM; another points to the Mac OS nanokernel and Multiprocessing Services giving a preemptive kernel with cooperative legacy apps on top, though adoption was limited.

BeOS vs NeXT and the Apple What‑If

  • Several commenters argue Apple was right to choose NeXT: BeOS reportedly had weak networking/printing, fragile C++ APIs tightly bound to a specific compiler/ABI, and a crash‑prone heavily multithreaded GUI.
  • The C++‑heavy design (with extensive subclassing and multiple inheritance) led to “fragile base class” issues; maintaining long‑term binary compatibility looked difficult.
  • Others stress that BeOS was quite POSIX‑like under the hood, but also note it had to implement that from scratch.
  • Management/culture is seen as the decisive factor: NeXT brought in a strong leadership and technical team; some ex‑Be management later struggled at Palm.
  • A few speculate that had Apple bought Be, it might have failed to recover; BeOS might have become “Unix with a different UI” over time anyway.

UI Concepts and Window Management

  • BeOS/Haiku’s tabbed titlebars prompt extensive discussion:
    • Tabs can be dragged, “stacked” together, and used to group windows from multiple apps into tabbed sets.
    • Haiku improves on BeOS with “magnetic” tabs that snap together; classic BeOS required manual alignment and didn’t keep windows tethered.
  • Some lament modern macOS titlebars turning into toolbars with minimal draggable area.
  • Several users praise Linux/X11 style “borderless” windows moved/resized by modifier+mouse, and note these behaviors date back to early X11 window managers.
  • Commenters recall BeOS‑inspired or fluxbox‑style tabbed window managers on Unix desktops and wish more modern DEs copied these ideas.

BeBox, GeekPort, and Hardware Hacking

  • The BeBox’s “GeekPort” sparks nostalgia; modern rough equivalents cited include Raspberry Pi GPIO headers, parallel ports (via PCIe cards), and USB GPIO bridges (e.g., FT232H).
  • BeBox production anecdotes highlight its hand‑assembled, hand‑painted nature; some owners still periodically boot theirs to keep it alive.

Nostalgia and OS Diversity

  • Motivations for revisiting BeOS/Amiga‑era systems include:
    • Pure nostalgia.
    • A belief that BeOS’s UI/UX felt genuinely better and faster than modern desktops.
    • Missing the 1990s–2000s era of many competing desktop OSes (BeOS, OS/2, etc.), versus today’s narrower mainstream choice.
  • BeOS is remembered by some as the best‑looking and snappiest desktop they used; they contrast this with perceived over‑complexity in environments like KDE.

Other Alternative OS Efforts

  • RISC OS is highlighted as another “clean, legacy‑free” desktop still maintained, especially on Raspberry Pi, with both open and commercial variants.
  • A Linux distribution (“V OS”) that ports the Be GUI and SDK onto a Linux kernel is mentioned as a lightweight potential alternative to GNOME/KDE, if it gains traction.