On August 26, 2026, the Haiku project released R1/beta6 — nearly two years after the previous beta (R1/beta5, September 2024), and almost exactly a week after the project’s 25th anniversary. Haiku is the open-source desktop operating system re-creating BeOS, built by a small team of mostly volunteers; the release notes page states plainly that no code or other materials generated by “AI” are used in first-party components. This release rolls up almost two years of the development team’s work, with over 530 bug and enhancement tickets resolved, and it is being called the most polished and stable release of the project so far.
What’s Inside
Two items stand out. First, browsers: after beta5, browsers based on the Firefox codebase started appearing in the software depots, initially quite buggy and without official branding. Over two years the ports stabilized, and Mozilla recently granted permission for the official “Firefox” name. HaikuDepot now also carries LibreWolf, Waterfox, Floorp, and Icedove (a de-branded Thunderbird) — x86_64 only for now. Second, virtualization: Haiku has picked up NVMM, the NetBSD virtual machine monitor, giving QEMU hardware acceleration on x86_64 hosts with Intel VT-x or AMD-V, supporting 32- and 64-bit guests and SMP, though it is still marked experimental. There is also a port of the Go compiler and runtime (version 1.26.1) in the repositories — enough to build Hugo, the static site generator that produces the Haiku website itself. Beyond the headlines, the release notes credit hundreds of smaller fixes across “practically every area of the system,” with the project’s monthly activity reports carrying the full accounting.
Performance: From git status to Full Builds
The release is dense with system-wide optimizations: MIME sniffing is 5–10x faster; pipe throughput rose from hundreds of MB/s to multiple GB/s; kernel locking granularity, malloc size classes (untouched since 2007), and the directory-entry cache were all reworked. The effects show up in real workloads. Running git status on a repository with over 160,000 files dropped from roughly 33 seconds to 20 seconds with a cold disk cache, and from 15 seconds to 2.5 seconds with a hot cache. A full rebuild of HaikuWebKit on the same buildhost took 4 hours 53 minutes on beta5 and 2 hours 33 minutes on beta6 — close to half. Memory management was overhauled too: a new userland allocator based on OpenBSD’s implementation plus a global caching layer, and 32-bit systems can once again boot with as little as 128 MB of RAM. The list goes on — rewrites of basic library calls like memmove and strcmp, pre-mapping heuristics for large executables that speed up compilers like gcc, and kernel malloc size classes that had not been retuned since 2007.
Catching Up on the Desktop
app_server — Haiku’s display server, window manager, and drawing server — can now restart after a crash and have all running applications reconnect and re-establish their state, no reboot required. The screenshot tool gained area selection; the team monitor groups child processes under their GUI parents; Tracker supports folder-filtering queries over the filesystem’s indexed attributes; SoftwareUpdater now cleans up old “previous states” automatically. Hardware compatibility improved substantially for machines from the last five years, more USB ethernet and Wi-Fi adapters work through the FreeBSD/OpenBSD driver compatibility layer, and POSIX coverage expanded with O_CLOFORK, kqueue with Haiku-specific objects, and more. Filesystem drivers saw serious work as well: NFSv4 received refactors and asynchronous I/O improvements, BFS optimized its free-block scan and query index selection, and the file-data cache now keeps one write queue per disk device — so a large copy to a slow disk no longer pretends to finish instantly and then stalls at sync.
Still in the Lab
The ARM64 port now boots all the way to the desktop under virtualization, and one contributor runs an unmerged branch on Apple M1 hardware. Multiprocess WebKit for the built-in WebPositive browser has progressed but is not ready. Neither feature shipped in beta6; the team chose to leave immature work on the development line rather than rush it into the release. Lower-level robustness got attention too — the guarded_heap debug allocator was rewritten, and low-memory behavior, notable in a system designed without an OOM killer, recovered from more failure states than before.
A 25-Year Project’s Operating Model
Haiku, Inc. is a 501(c)(3) non-profit funded by donations, and for this entire release cycle it employed core developer waddlesplash as a contractor — the contract continues today. Much of this release’s stability is, quite literally, purchased time. The project also added one new committer (Zardshard) and reports over 3,900 open tickets and 16,000 closed ones on its bug tracker. In 2026, with AI-generated code flooding every repository, a 25-year-old project that states it uses no AI-generated code still shipped a near-2x compile-time improvement. The lesson about long-haul open-source desktop development is unchanged: funding, patience, and unglamorous engineering fundamentals.
Sources
AI-assisted summary compiled from the sources above, reviewed by a human before publishing.