Linked by Thom Holwerda on Mon 10th May 2010 10:03 UTC, submitted by robertson
Two news items about alternative operating system news in a row? What is this, Christmas? In any case, the Haiku project, the darling of OSNews (hey it's okay now), has released its second alpha release. This new stable development release contains some serious improvements over the first alpha.
Thread beginning with comment 423587
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: At the risk of pissing off the fanbois...
by drcouzelis on Mon 10th May 2010 18:11
in reply to "RE[2]: At the risk of pissing off the fanbois..."
Member since:2010-01-11
Add multiuser support and it starts to look like a very nice OS.
There is experimental multi-user support, although I haven't tried it. Haiku already does a pretty good job of separating the parts that the user is allowed to change and the parts that the user shouldn't touch.
Including bash might lead to people actually writing bash scripts which is generally a Very Bad Thing
Why is writing Bash scripts a bad thing?
RE[3]: At the risk of pissing off the fanbois...
by kedwards on Mon 10th May 2010 19:37
in reply to "RE[2]: At the risk of pissing off the fanbois..."
Member since:2009-04-25
Why would they ditch the Haiku API after 9 years of hard work?
Besides QT programs being cross platform, I just don't see any other benefit to use QT API over the Haiku API. Saying nobody is going to learn the Haiku API because they can write code in QT is like saying nobody is going to learn the Cocoa framework because they can write code in Mono.
How is writing Bash scripts a bad thing?
RE[4]: At the risk of pissing off the fanbois...
by nt_jerkface on Tue 11th May 2010 05:07
in reply to "RE[3]: At the risk of pissing off the fanbois..."
Member since:2009-08-26
Besides QT programs being cross platform, I just don't see any other benefit to use QT API over the Haiku API.
How about Qt Creator?
Why should developers bother learning the API of an OS that doesn't have a userbase? Because you think the system is cool? Yea good luck with that.
Building around Qt is good advice. The Haiku team needs to remember that most developers do not share their nostalgic attachment.
Member since:
2006-07-25
They should clearly transition to Qt being the native Haiku toolkit. It is very good, well supported and has lots of pre-existing code.
Nobody is really going to learn the BeOS API if they can write stuff in Qt and have it work on windows, linux and mac too.
Add multiuser support and it starts to look like a very nice OS. I wish they had left bash out though. Including it might lead to people actually writing bash scripts which is generally a Very Bad Thing(tm).