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 334832
To read all comments associated with this story, please click here.
by UltraZelda64 on Fri 24th Oct 2008 04:28 UTC
Member since:

Now, I don't mean to put down anyone's work, and I appreciate what the ReactOS guys are doing. But I can't help but be impressed with how (relatively) feature-complete and stable Haiku seems to be already... and they claim it's not even an alpha yet (but close). I'm used to ReactOS crashing within 2-5 minutes, which is part of the reason I didn't bother trying out Haiku originally (that, and I'm not that familiar with QEMU, and my computer can barely handle it). My first Haiku session lasted over an hour, which was when I got out of memory errors (but strangely, Haiku said it was only using 88 megs out of 128).

I would assume that this is primarily because Windows is so radically different and "unknown" while BeOS is POSIX-compliant and not quite as different (though I'm sure a decent chunk of reverse engineering needed to be done). Any ideas? Also, anyone know how many people are working on the two projects? Maybe BeOS just has a bigger fan base.

Reply Score: 4