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.
Permalink for comment 335111
To read all comments associated with this story, please click here.
RE: Please explain
by umccullough on Sun 26th Oct 2008 20:42 UTC in reply to "Please explain"
umccullough
Member since:
2006-01-26

I wonder, how do the developers retain compatibility with BeOS? Do they have listing of the complete BeOS api somewhere and try to implement it? Have they reverse engineered BeOS? How do they know Haiku is compatible with BeOS?


That's the neat part about public headers provided for development on a given platform...

And thus, it's only guaranteed to be binary compatible from a public API perspective.

The kernel is very BeOS-like.

The API is pretty well documented and available for all:

http://www.haiku-os.org/legacy-docs/bebook/

Reply Parent Score: 2