Linked by Thom Holwerda on Thu 23rd Oct 2008 19:58 UTC, submitted by FreeGamer
BeOS & Derivatives It seems like only yesterday when due to a combination of hubris, bad business decisions, and pressure from Apple and Microsoft, Be, Inc. went under, with its assets - including the BeOS - bought up by Palm, who now store it in a filing cabinet somewhere in the attic of the company's Sunnyvale headquarters. Right after Be went under, the OpenBeOS project was started; an effort to recreate the BeOS as open source under the MIT license. This turned out to be a difficult task, and many doubted the project would ever get anywhere. We're seven years down the road now, and the persistence is paying off: the first Haiku alpha is nearer than ever.
Thread beginning with comment 335164
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[5]: Please explain
by umccullough on Mon 27th Oct 2008 21:43 UTC in reply to "RE[4]: Please explain"
umccullough
Member since:
2006-01-26

How do we know Haiku kernel is as good as BeOS kernel? We dont have the BeOS code?


That's what benchmarks are for ;)

Already, the Haiku kernel performs many operations faster than BeOS did.

Often times reading the code does not reveal its relative performance, that actually takes real-world tests anyhow. The "performance" of BeOS wasn't necessarily a result of any special coding tricks that only Be, Inc. coders knew, but rather certain design decisions that Haiku also follows in many cases.

I think if there was ever a comparison made between Haiku's code and BeOS' code, we'd find that the Haiku code might be cleaner and better-written largely because it's FOSS, and built from the ground up to re-implement the same functionality as BeOS.

The kernel Haiku forked from was NewOS, which was written by an ex-Be engineer originally.

Reply Parent Score: 2

RE[6]: Please explain
by ari-free on Tue 28th Oct 2008 00:37 in reply to "RE[5]: Please explain"
ari-free Member since:
2007-01-22

a lot of BeOS performance was really responsiveness and that's not easy to benchmark.

Reply Parent Score: 2