Linked by rohan_p on Wed 8th Aug 2012 15:21 UTC
BeOS & Derivatives BeOS may be dead, but over a decade after its lamentable demise the open source Haiku project keeps its legacy alive. Haiku is an attempt to build a drop-in, binary compatible replacement for BeOS, as well as extending the defunct OS's functionality and support for modern hardware. At least, that's the short-term goal - eventually, Haiku is intended significantly enhance BeOS while maintaining the same philosophy of simplicity and transparency, and without being weighed down with the legacy code of many other contemporary operating systems. Computerworld Australia recently caught up with Stephan Assmus, who has been a key contributor to the project for seven years for a lengthy chat about BeOS, the current state of Haiku and the project's future plans.
Thread beginning with comment 530479
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[4]: Haiku and Linux
by tidux on Thu 9th Aug 2012 18:53 UTC in reply to "RE[3]: Haiku and Linux"
Member since:

You'll have to wait for R2 for a fix for that. R1 is supposed to be a drop-in replacement for BeOS R5, and that means pure single-user. R2 is where Haiku will start to take off on its own direction.

Reply Parent Score: 2

RE[5]: Haiku and Linux
by moondevil on Thu 9th Aug 2012 19:10 in reply to "RE[4]: Haiku and Linux"
moondevil Member since:

Yeah, but all other systems keep moving on as well.

GNU/Linux only managed to achieve what it is today thanks to the support of companies that wanted to improve the ecosystem for their purposes, regardless of good or bad.

Haiku needs something similar, otherwise it will never be much more than a hobby OS.

Nice to cure the nostalgia kick for a few hours and that is it.

Reply Parent Score: 3

RE[5]: Haiku and Linux
by cipri on Thu 9th Aug 2012 21:40 in reply to "RE[4]: Haiku and Linux"
cipri Member since:

but the haiku at the moment says: we finish R1, then we continue with R2.
But they could do something different. They could already now start working on R2 while also working on R1. And if something in R2 would be important to R1, it can be ported back to R1. For example while R1 is not finished, the R1 version could be the "official release", and the R2 would be just something like a prototype which doesnt need to be backward compatible with each release. And just after R1 is finished, the R2 becomes the "official version", which from there on needs to be backward compatible and not break api/abi. This kind of "freedom" perhaps could help to make greater progress and to come-up with new ideas.
There should something like an "experimental haiku", in my vision.

Reply Parent Score: 2