Linked by Thom Holwerda on Tue 10th Feb 2009 18:31 UTC
BeOS & Derivatives Back when it was becoming clear that the time of the BeOS had come and gone, enthusiasts immediately set up the OpenBeOS project, an attempt to recreate the Be operating system from scratch, using a MIT-like license. The project faced difficult odds, and numerous times progress seemed quite slow. Still, persistence pays off, and the first alpha release is drawing ever closer. We decided to take a look at where Haiku currently stands.
Thread beginning with comment 348315
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: But why?
by geleto on Wed 11th Feb 2009 20:51 UTC in reply to "But why?"
geleto
Member since:
2005-07-06

In today's world, besides nostalgia, why would I want to use Haiku?

While on the surface both Windows and Linux look quite nice - under the hood we have one big mess. Layers upon layers of APIs, libraries, services, frameworks and subsystems.
On Haiku - you have a beautiful and consistent API, well defined kits (app/interface, filesystem, input, kernel, media, network, translation, etc). Everything is modular, integrated and consistent - it's so much easier to understand what's going under the hood. Even browsing the source code - it's sooo much less intimidating than looking at the Linux Kernel or X.Org sources.
This results in greater stability, responsiveness and speed. Extending Haiku and adding new features will be much easier and faster, even with less developers.

Reply Parent Score: 2