Haiku in media


Yes, that was expected since Haiku was already in their database since the last alpha. DW monitors all entries for new releases except for those in the waiting list.


And I will be sure to have a full Haiku review, holding nothing back, on YouTube, my personal blog, and wherever else I can get the word out that the beta is here. And I’ll be sure to post links once they’re all ready! :smile: Woohoo for beta!


Haiku Beta was just featured on Bryan Lunduke’s show:


https://linuxunplugged.com/269 it starts at around 23 minutes.


A Dutch tech website published a mostly copy/paste ‘article’, but at least the site is pretty well known.


It was a memorable experience, including the road trip crossing most of France and Germany with another GSoC student and two Haiku devs to get to the event,” he said.

Oh, shared memories @PulkoMandy !


Not a review, but a tweet from KDE-Community.


I’ve been keeping especially close track of the news, and have noted a bunch of articles that aren’t linked here on the main wiki: https://dev.haiku-os.org/wiki/R1/Beta1/InThePress


Nice job. The beta got lots of coverage, and here is a summary of ppl’s opinions in rough order of prevalence:


  1. Speed
  2. Stability
  3. Bringing back nostalgia of BeOS
  4. Quality coding
  5. Potential gaming platform


  1. Browser/s not as feature-full as on other OSs
  2. Internet connection problems
  3. Lack of 3D graphic acceleration
  4. What new features does it offer over other OSs?
  5. Apparent lack of software in package manager and 3rd party repositories
  6. Extensive C++ code
  7. MIT licence

These feedbacks should provide good ideas for future development. For example, few cared for the various features that Haiku posesses - like multithreading, tiling, database-like filesystem, etc - because they can be had on other OSs. What ppl noted the most was its speed. So this could be Haiku’s main advantage over other OSs. Future development could involve 3D graphics capability, and creating / porting applications that are reliant on speed: like audio & video editing, and games. Note that the gaming industry has been a major force in computer advancement. So getting some top games to run on Haiku at good speed would be enticing to that industry. Who knows, maybe then the claim could be made that Haiku is the fastest OS in the world for graphic-intensive applications.

However, if Haiku keeps being promoted as a “general purpose OS” it looks like it could be hard to get regular users. What do others think?


Normal users will say goodbye very quickly!
Why I’m still hanging around here is puzzling to me …


As what else could it be promoted? A gaming OS without (hw-accelerated) games? A high-end A/V OS without hw-acceleration and pro apps? A server OS without the needed optimizations to put it ahead of Linux et al.?

The perceived speed of Haiku is the responsiveness of the GUI, not that it somehow computes faster than other OS when running higly tuned software like A/V or games.
A responsive GUI is the foundation of a good desktop OS. On that basis you can run all sorts of different apps. The Haiku project works to improve this foundation, what apps get created and used is up to the different users.
As implementing hw-acceleration and all the needed drivers is a huge task, I suspect we won’t see many apps relying on that for some time.
And wishing for it, unfortunately, doesn’t help… :slight_smile:

Obviously, you’re not normal! :grin:


I like the installation fast as blinking to the destination, and gui responsiveness.

Even with the shortest Linux install that i made, you cant beat it, and you get a bundled OS with GUI, compilation tools, web browsing and multimedia capabilities. I like to have it in a usb drive to boot on my main system.

The worst part (for me) is the lack of general drivers to handle real hardware, so it could be installed with less KDL travels, more than having hardware acceleration. But i know that developing them is a hard work.

I agree on reading about not having a “common” browser too, but wont matter much if you cant boot the OS first :thinking:


C++ code (when well written) and the MIT license are hardly Cons… if anything a hardline C only kernel would make things worse.

And your isues 1,2 and 3 are sort of intertwined… Implementing a full featured browser these days practically requires hardware acceleration.

Internet connection problems, I assume you mean wifi… its been through alot of changes lately instability is to be expected.


The 2 youtube tech reviews - Lunduke @ Linux Unplugged - were very positive about the system’s technical merits - particularly the speed, pervasive multithreading, and ease of booting and installing apps. They noted how unique the OS was in the computing world.

But comments from everyday users on the news websites were mostly brief. This suggests that they just tried it for a while and then went back to their usual OS. This is more worrying because an OS has to quickly capture the users interest or they will get bored and not return. This is where things have to work - drivers, internet, browsers particularly - and the desktop has to be easy to navigate and pleasing on the eye.

So according to the tech guys it’s still a modern system, but to everyday users it might have a dated look and feel.


One cannot please everybody.


From an entirely end-user point of view, it’s hard to argue with some of the Cons. The hardware acceleration issue doesn’t crop up in my immediate use on a personal level since I’m a multi-OS person with a specific end goal for my time spent on Haiku- productivity. For everyday users and potential gamers and developers attracted to the OS, though, this is a hurdle that I’m sure Haiku will be able to deal with.

We see the same issue with Linux historically; in the beginning (and seventeen years of development or not, the Beta really does mark the beginning of Haiku as far as the general public is concerned) it had incredibly limited hardware support, to the point there were tools to determine whether your system could run Linux at all or not. A growing user base, though, translates into a greater support system and a more well-rounded batch of drivers and kernel support for hardware. It may take a full release or two for this to pick up speed, but it will come, and hopefully those releases will become more regular and timely to show the community at large there’s a good reason to build on the support side than just complaining about the lack of support or opining on how to hack it together.

The browser issue is a problem for end-users. PulkoMandy does good work on WebPositive, but a full featured browser is a lot for one person to manage. In the 6+ months I’ve been using Haiku I’ve seen good growth there, and while it might not be Firefox or Chrome, I do find myself using WebPositive more than Qupzilla now, as it does work a lot better than it used to.

I’m not sure Con #4 is much of a Con as it is a question that hasn’t been clearly laid out for the layman yet. Haiku offers quite a bit that Windows and Linux do not. Stack and Tile alone are great end-user features that don’t get quite enough hype in these articles. The GUI might not seem the most up-to-date when compared to the look and feel of Gnome and Windows 10, or the cultish love even regulars here seem to have for the big animated mess of a dock MacOS uses, but the handling and controls around it around it are great and responsive.

Unfortunately, though, when it comes to attracting Windows users it’ll always be an uphill battle with hardware support and gamers, and when it comes to attracting Linux users they’ll be looking for customization and software alternatives that perform in a manner they’re used to getting from Linux’s community. While the latter will certainly come in time for Haiku as well, the former is going to be on everyone’s minds for a while and will continue to show up in press reviews of the OS as benchmarks of usability.

Haiku’s team are not stupid, though, they’re skilled coders working with what time they have to make something they’re passionate about, and I don’t doubt they’ll keep plugging away at these issues. The key, though, is going to be explaining why these issues exist in the first place and keeping the press informed about how development happens and how inclined persons can get involved. As it grows from Beta on, it’s going to take more than the current handful of devs to maintain the project and see that these things are addressed quickly enough to keep the appearance of moving forward to attract users and new devs.


@waddlesplash Haiku Beta is featured in November edition of Linux Magazine: http://www.linux-magazine.com/Issues/2018/216/Review-Haiku


That’s pretty cool … but it’s also the most inaccuracy-plagued article about Haiku I’ve ever read. Did they just read Wikipedia? Maybe not, because it knows about the in-the-works 32-bit compatibility layer, but it also says that was already merged. It also says that we have an “i915 Direct Rendering Manager” driver which “supports hardware acceleration”, “most Broadcom chips are supported”, etc.

Pretty baffling, especially as I thought LinuxMag was supposed to be reputable…


I posted a reply comment to that article, but I’ll leave it here also for posterity’s sake (and in case it disappears over there?):

Hi, Haiku developer here. Thanks for covering us, but … this article is wildly inaccurate:

  • We are not a “microkernel OS”; we have a monolithic kernel with slightly hybrid tendencies. We use dynamic kernel modules almost exclusively in a way Linux and the BSDs don’t, and support FUSE, etc.; but by-and-large all hardware drivers and other such modules run in kernel space. I’m not sure where you got this from; even our Wikipedia page lists us as having a “hybrid kernel”.
  • We are most definitely a UNIX system. The fork()-based process/memory model, /dev, command pipes, etc. are deeply ingrained into the OS itself; and there are plenty of POSIX concepts which have no “Haiku API equivalent” (and if they do, usually the “Haiku API equivalent” wraps the POSIX API, not the other way around.) So we are POSIX-compliant and thus a UNIX, not just by a “compatibility layer”.
  • OpenBFS is the name of the driver, BFS is the name of the filesystem itself.
  • The name of the project is “Haiku”, not “Haiku OS”; this is handled correctly in some parts of the article and not others (but this is a common mistake at least.)
  • The project founder quitting in 2007 did not “leave the project’s future uncertain”, most of our major activity has occurred since then, as you can see; and the mailing list response at the time shows this was a major but not “earth-shattering” event.
  • We have had more than 100 people submit patches over the years, it’s true, but more properly there are only about ~35 people with direct commit access.
  • Haiku 64-bit does not have a 32-bit compatibility layer yet. One is in the works and has been published to a feature branch but it certainly has not been merged and is not in the beta or the nightlies, as the article states.
  • The WiFi/ethernet drivers are from FreeBSD, not just compatible with it.
  • Then there is this section: “work on Intel’s hardware acceleration in Haiku has been a focus, which currently has born fruit. The i915 Direct Rendering Manager (DRM) driver in Haiku now supports acceleration for all of Intel’s HD/Iris chips” – which is completely and totally wrong. We don’t have hardware acceleration of any kind on this hardware or any other hardware, though there are plans to work on it, they are currently just plans. The GSoC 2017 project didn’t go anywhere. (Where did you even get this information?)
  • “Even if Haiku boots fine but remains offline, there is little you can do to set up the system” – set up as in install? I’m not sure what this means. You can install the system offline without any issues; in fact the installer does not even need an internet connection.
  • “However, most Atheros and Broadcom and some of the Intel Pro wireless chips” – um, it’s pretty much the other way around: most Intel Pro, almost all Atheros, and some (i.e. virtually none at all, only a few from 2010 or so) Broadcom wireless chips.
  • “Downloading and installing a nightly image is preferable for new users, because this offers the latest hardware support and the most recent software additions.” – At this point the beta is preferable, for a variety of reasons, mostly related to system stability and performance tweaks, and nightlies have gone back to being “bleeding edge.”
  • “The aging Alpha R4.1 version doesn’t have HaikuDepot, which is why it might not be the best choice for new users” – R1a4.1 is no more (Maybe this article was written before beta1 came out, and just was not properly updated before publishing?)

So, all in all, that is most of the major facts about Haiku this article has which are just wrong. This is kind of ridiculous, really.


This comment is more informative than any article I read about Haiku. :smile: :+1: