BFS, the kit-based C++ API, and the pervasively multithreaded design behind BeOS's open-source successor.
A complete walkthrough Haiku's Terminal application and its bash-based shell — familiar to anyone with Unix experience, with a few Haiku-specific tools worth knowing about.
A complete walkthrough setting up Haiku's native WebPositive browser day to day — organizing bookmarks, configuring privacy and cookie behavior, and setting a sensible download location.
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.
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.
A live query doesn't just return files matching a condition once — it keeps the result set current automatically, as files are created, changed, or deleted, for as long as the query stays open.
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.
Haiku's Media Kit models audio and video processing as a graph of connected nodes passing buffers to each other in real time — the same conceptual model professional media software still uses today.
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.
After a design drafted in January 2011 and development under funded contracts, Haiku's packagefs-based package management shipped in September 2013 — reshaping how software gets installed on the system.
The first beta release of Haiku R1 arrived on September 28, 2018 — a milestone that had been anticipated for years, marking the project's transition from alpha-quality software toward an eventual stable 1.0.