To read all comments associated with this story, please click here.
There's not a whole lot of point if you're just running Qt & Java applications. Linux already does that pretty well. Speed, simplicity, and integration are some of Haiku's main features, all of which are lost when using non-native software. (It's a necessary evil for now.)
IOW, Haiku will never be better at running Linux software than Linux, and becoming something akin to just another distribution isn't the goal.
Uh really? It seems very wize to me!
I would criticize them over using an unknown kernel instead of using the FreeBSD kernel or Linux but not over this!
What is amusing is that the main reason for not using Linux (X) is being replaced by Wayland, the replacement will take a few years, but it's still much less time than having Haiku working "by default" on a PC (i.e not having to carefully select the part of a PC to make it run Haiku natively).
Most FreeBSD drivers can be re-compiled for Haiku with minimal change.
Haiku has pretty awesome hardware support for a niche OS - and it is getting better continually.
The NewOS kernel was chosen because it required the least amount of work to gain BeOS binary compatibility because it was created by a Be engineer...





Member since:
2005-08-07
Definitely not Haiku, if anything the ones to bear that dubious honor would have to be ReactOS IMHO... I mean geeze guys pick a release to standardize and build from there to completion before trying to play catchup to the latest versions of whatever.
I know the Haiku guys have gotten a lot of flack over their choice to hold fast to reimplementing BeOS R5 before commencing to update and modernize where needed, but after watching the result of the continually moving guideposts with ReactOS... Well I'm glad that Haiku had a concrete goal and roadmap to follow. Seems to have been helpful to them in the long run.
--bornagainpenguin