BFS, the kit-based C++ API, and the pervasively multithreaded design behind BeOS's open-source successor.
On September 14, 2009, eight years after OpenBeOS began, Haiku shipped its first version the public could actually download and boot — as a live CD, something BeOS itself never offered.
A walk through what actually happens between powering on a Haiku machine and reaching a usable desktop, and where things most commonly go wrong along the way.
Released December 23, 2022, roughly a year and a half after Beta 3, Haiku's fourth beta continued the project's pattern of steady, incremental refinement toward an eventual non-beta R1 release.
Released June 9, 2020, roughly two years after Beta 1, Haiku's second beta arrived as much of the world was under pandemic lockdown — with volunteer development continuing largely uninterrupted.
Founded in July 2003 by Michael Phipps in Rochester, New York, Haiku, Inc. gave the OpenBeOS/Haiku project a formal nonprofit structure for accepting donations and funding contractor work.
Installing a package on Haiku doesn't copy files onto disk at all — it mounts the package itself as part of a virtual file system, which is exactly what makes activation and rollback instant.
Haiku's native C++ API isn't one monolithic library — it's a set of separately-scoped 'Kits,' each owning one concern, that together define what writing software for Haiku actually looks like.
Haiku applications don't poll for events in a manual loop — they define Handlers, and let a Looper thread dispatch messages to the right one automatically.
BFS treats extended attributes as first-class, indexable data — turning ordinary file queries into something closer to a database lookup, decades before this became a mainstream idea.
Haiku's kernel wasn't built as a Unix variant with threading bolted on — it was designed around threads as the fundamental unit of execution from the very beginning.