Linked by Thom Holwerda on Mon 20th Mar 2006 23:07 UTC, submitted by Tako Lansbergen
BeOS & Derivatives Studio33 has released part II [part I] in its series of articles looking at the current state of Haiku. "In the previous part I talked about the achievements of the Haiku Team since the project was first started, this time I will go deeper into the work that has been done lately and which parts need serious attention in the coming months." Screenshots o'plenty, boys and girls.
Permalink for comment 106332
To read all comments associated with this story, please click here.
RE: X11 compatability
by ronaldst on Tue 21st Mar 2006 12:27 UTC in reply to "X11 compatability"
Member since:


In the future, Haiku really needs to implement some sort of compatability port of X11 (similar to what Wine does for Win32). There's no compelling reason for me to use Haiku R1 over linux at the moment. It's bad enough I can't run Windows apps--now I can't use linux apps as well?

IIRC it wasn't the X11 that was the problem but more of missing kernel instructions (NMAPsomethingamajig).

I realize what the goals of Haiku R1 are, nobody needs to remind me. But let's face it, if Haiku is planning on becoming mainstream it must have a decent app collection. In my opinion, the easiest way to do this is to be compatible (source-compatible at least) with linux apps. I think I'd be more interested in an R2 release which looks outside the box, then a boring R1 release which is basically a clone of an extinct BeOS. Just my $0.02.

The original BeOS r5 was already more than 90% POSIX compatible. One of the aim of the rewrite was to fix that last problematic percentage.

A decent QT 3 toolkit port to BeOS/Haiku would be best.

Reply Parent Score: 3