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.
Permalink for comment 516076
To read all comments associated with this story, please click here.
RE[5]: Uh what
by Brendan on Sat 28th Apr 2012 15:38 UTC in reply to "RE[4]: Uh what"
Member since:


"While Haiku does support POSIX, it is not a "POSIX system", and not a *NIX. POSIX is simply an addition, not the base for it.

Correct me if I'm totally wrong here, but POSIX on Haiku is a first-class, and in many cases the only, API[1].

Ok, you're wrong. The primary/native API used by Haiku is the same API that was used for BeOS. This API is described here:

Notice that it looks nothing like POSIX.

I'm not sure how well integrated their POSIX API actually is; but I also doubt it matters. Haiku/BeOS is different (lots of message passing and multiple threads) and applications designed for POSIX (that don't use message passing, etc) will always be a poor fit regardless of how well implemented the POSIX API is.

Unfortunately, for a new OS there's always a "chicken and egg" problem - it's hard to attract developers when there's no applications and hard to get applications without developers. I'd assume that the only reason they bothered with POSIX at all was to break this "chicken and egg" problem (by making it easy to port "better than nothing" applications from elsewhere).

- Brendan

Reply Parent Score: 1