Linked by Thom Holwerda on Fri 27th Apr 2012 22:00 UTC, submitted by koki
BeOS & Derivatives "Ultimately, Haiku represents a different way of viewing your personal computer. If you think that software shouldn't be riddled with bugs and incompatibilities and inefficiencies, if you hate being forced to swap out your hardware and software every few years because 'upgrades' have rendered them obsolete, and if you find that the idea of using an operating system that's fast, responsive, and simple is refreshingly novel and appealing, then maybe, just maybe, Haiku is for you." What fascinates me the most is that Haiku's not working on a tablet version. How delightfully quaint.
Thread beginning with comment 516261
To read all comments associated with this story, please click here.
by Valhalla on Mon 30th Apr 2012 00:55 UTC
Member since:

Despite being a huge Haiku fanboy (former Beos fanboy, as I suppose many of us are) I have to say that some of the salesman lingo in this article made me cringe.

At the same time I think we need to cut the author some slack, Ryan Levengood is a developer who has contributed to Haiku (like the native browser) and as such is likely even less objective than sideline fanboys like me.

As for the native api/posix debate, Haiku aims to be posix compatible (that's not to say it's ever going to be fully posix compatible). This is important since unless Haiku really takes off which seems improbable, it will have to rely heavily on ported software, and lots of open source software today needs posix support.

As for the native API, it's showing it's age. There's been an awful lot of things happening in C++ back from when the Be api was defined not to mention in overall api design I'm sure, recently one of the core developers Ingo Molnar brought up the suggestion of replacing the native Be api with QT (not sure how I feel about that).

So why should anyone care about Haiku, is it faster than say Linux? No, atleast not when I did benchmarks of my own code (which admittedly was quite some time ago), but it is more responsive under load.

Note, responsive means that I notice very little to no impact (lag) when for instance copying large files in the background, something which always happens in Linux unless I do ionice or run a patched kernel. In reality the file copies are obviously slightly slower (there's no magic thing they do in order to increase responsiveness, you basically choose responsiveness over throughput) but that doesn't matter since this is a desktop OS and on the desktop I've always felt that nothing trumps responsiveness.

But the biggest draw for me has always been how it's a operating system built as a whole, from kernel to gui, to sound. It's a complete desktop system from top to bottom where nothing feels 'tacked' on.

Sadly I have to admit I seldom boot into my native Haiku partition these days, and the times per month I boot it up in the VM are indeed getting fewer. The problem is as often that of software, Haiku is simply starved. This in turn is due to a problem of attracting developers/porters.

Will Haiku ever hit the critical mass needed for it to gain a healthy software ecosystem with ports of key software like Firefox/Chrome, LibreOffice, Blender, Inkscape, Gimp etc (and possibly even some strong native software) ?

Impossible to say, but as long as the devs keep chugging along, making Haiku better with every day and with new developers joining in there's hope. And with things like Summer of Code and the community raising funds for time-based full-time employment of developers I'd say there's plenty life in there yet!

Wow, longwinded, sorry!

Reply Score: 2