Linked by Thom Holwerda on Thu 23rd Oct 2008 19:58 UTC, submitted by FreeGamer
Permalink for comment 334832
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
More News »
Sponsored Links



Member since:
2006-12-05
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.