Poetry is in motion. The Haiku Project, its developers and team members announced the Haiku operating system released its third beta release, version R1/Beta3, July 25th, 2021. Version R1B3 continues the trend of more frequent releases to provide users and developers with an up to date and stable platform to work on.
This release combines the best of Haiku’s history as a spiritual successor of BeOS and the hard work of a passionate community. It provides several new features and performance improvements that make Haiku even better.[…]
WebKit, the backend of the bundled web browser developed by the Haiku team, WebPositive, received multiple major improvements. This provides a good base for further improvements as well as an improved browsing and website rendering experience in WebPositive, which developers will continue to focus on for the next release, Beta 4 and as Haiku nears its first initial release, R1.
Going from beta 2 to beta 3 is a giant leap if you haven’t been keeping up. Haiku is much farther along than people think, with the biggest drawback being, as always, that hardware support is going to be a mixed bag. Haiku is still every bit as clean, fast, and enticing as the original BeOS was over two decades ago, and I’ve scored two junkyard office PCs to see if I can get a proper Haiku box running.
Weird parallel Thom; I have two “junkyard” machines for testing OpenBSD and Haiku respectively. One is a Dell tower server from 2011 with a low power AMD GPU added for desktop use, long out of support from Dell and Microsoft but perfect for obscure OSes. The other is a mini-ITX system thrown together from scavenged parts, a bit newer with an AMD A10 APU. The former is running the latest OpenBSD snapshot, the latter is waiting on a new power supply and it will be my new Haiku playground.
Since I went minimalist and no longer develop software I threw all my old stuff out. If I had my way I’d be developing high performance graphics software and still testing it against a P200 and first generation dual core CPU to give compatibility and scaleability a good thrashing. The thing with producing software for a constrained system is it encourages you not to get sloppy and code stuff simple and lightweight and fast. Very fast. People get lazy and complacent with ninja development platforms and start adding in fat frameworks which add latency and lots of other horrors into the critical path. There are or were companies out there with a room full of clunkers so they could do this. None that I hear of now. Apparently Microsoft gave this up too and now simulate everything.