Haiku R1/beta6 Ships With Firefox, Go Support, and 530+ Fixes
Haiku, the open-source desktop operating system inspired by the defunct BeOS, released its sixth beta on August 26, 2026. The release came about a week after the project's 25th anniversary and closed over 530 bug and enhancement tickets across the codebase (Haiku release notes).
For those unfamiliar, Haiku is built from scratch in C++ with a design that emphasizes modularity, pervasive multithreading (meaning the system spreads work across many concurrent threads rather than relying on a single main thread), and a unified API for app developers. The project started in 2001 and has been working toward its first stable release, called R1, ever since. Each beta has chipped away at the gap between the system's ambitious design goals and everyday usability on standard hardware.
The most consequential change in beta6 is improved application compatibility. Many more third-party applications now run, including Mozilla Firefox, which had been a longstanding gap for the platform (Phoronix). For an operating system whose survival depends on convincing developers and users that it can run the software they need, getting a modern browser engine working is a meaningful threshold. Firefox on Haiku had been attempted through various porting efforts over the years without reaching a state ordinary users could rely on. Its inclusion in a beta suggests the underlying compatibility layers, particularly the POSIX subsystem (the set of standards that lets Unix-like software run) and the graphics stack, have matured enough to support a complex, externally maintained codebase.
Beta6 also ships with a port of the Go programming language (Phoronix). Go's toolchain has specific expectations around system calls, threading, and networking, so a functional port is a reasonable stress test of the OS's POSIX conformance and runtime environment. For developers already invested in Go, it lowers the barrier to writing and building Haiku-native services and tools. For the Haiku project, it widens the language ecosystem beyond the C/C++ core and the scripting languages that had working ports in earlier betas.
On the hardware side, the release notes recommend at least 2GB of RAM for 64-bit builds (Haiku release notes). That floor is modest compared to mainstream desktop Linux distributions or Windows 11, both of which typically recommend 4GB or more for a functional desktop session. The low requirement fits Haiku's architectural heritage: a system designed for responsiveness and single-user desktop workloads, not for running a server fleet or container orchestration.
The two-year gap between beta5 and beta6 is longer than the intervals between some earlier betas. Haiku has always been a volunteer-driven effort with a small core team, and release cadence has varied accordingly. The volume of resolved tickets, over 530, indicates sustained development activity even if the calendar gap looks wide. The fixes and enhancements span the kernel, app server, network stack, package management, and userland utilities, according to the release notes.
The broader context here is about what these additions mean in practical terms. A desktop OS that can run Firefox and host a Go toolchain is in a qualitatively different position than one that cannot. The browser is the primary application for most desktop users; without a functional one, an operating system is effectively excluded from daily use regardless of its technical merits. Go support opens a path for backend and command-line tooling that modern developers expect on any platform they deploy to. Neither addition makes Haiku a replacement for Linux or macOS, but together they push the project past a usability boundary that earlier betas did not cross.
The 25-year arc of Haiku is itself worth noting. Projects of this scope, undertaken without commercial backing, rarely sustain development across decades. Haiku has. Whether R1 ever ships as a stable release is an open question, but each beta narrows the remaining gap, and beta6 narrows it more than most.
