Linked by Thom Holwerda on Wed 18th Aug 2010 21:02 UTC, submitted by koki
BeOS & Derivatives "Back in mid-2001, when the news that Be Inc. had sold its intellectual property to Palm hit the streets, what many had suspected and rumored for quite some time - that BeOS development was headed towards closure - finally became a reality. This news and the sad realization that it ensued hit hard the developers and users of BeOS; but many of them did not give up on the idea of letting the operating system of their dreams die, and instead embarked on the daunting task of recreating BeOS in an open source fashion. This is how OpenBeOS - now known as the Haiku Project -- was born."
Thread beginning with comment 437429
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Not bad..
by BlueofRainbow on Thu 19th Aug 2010 11:26 UTC in reply to "Not bad.."
Member since:

Actually, not good since Haiku 1.0 is still only as an alpha stage release candidate. I'm hoping that it will take them less than the ~3 years and 6 betas it took for eComStation to go from alpha stage to final release.

I'm quoting interesting bits from Eugenia's original article and revisiting them.

"AtheOS, SkyOS had something usable by a three-years time, and remember, they only employed 1 developer each."

AtheOS has been forked and has become Syllable and now has a large development team. However, the original kernel has been retained only for the desktop version while the server version is based on the Linux kernel. SkOS has been stagnating for a few years now and may never reach 1.0 status.

"Most people don't care anymore (and why should they? No one wants to support an OS that sees official OS updates). And if Haiku is "ready" by 2010, no one will care. Too little, too late. What's the point re-implementing BeOS in a way to even have binary compatibility and targetting the functionality of BeOS 5, when by 2010 Longhorn 2, Mac OS X 12 and a more mature Linux will be available offering out-of-this-world features?

Is there a coincidence to the 2010 estimate date for the readiness of Haiku 1.0 or a realistic guess? What was not envisioned then is the rapid development of the mobile devices (and netbooks) and the arrival of Android, iPhone OS, Windows 7 Phone.....and touch graphical user interface.....

"Haiku needs to move on, it needs to re-set its goals, simply because its current goal, has already failed through market irrelevance. Timing was important for that goal, and now it's just too late trying to "sell" a BeOS 5-alike OS to the world. I would suggest creating an OS that tries to innovate and competes with future/modern OSes, while keeping its BeOS roots and code, but not by copying Be's mistakes and the irrelevant, right now, overall BeOS experience one could get out of a BeOS 5+."

Faster earlier development might have lead to currently having Gobe Productive 5 on Haiku.....rather than not even having a port of Productive 3 (which is now more than 5 years old) from its Windows commercial release. It's difficult to seriously consider an OS from a general user perspective when there is not even the equivalent of an integrated document generator/processor.

On the other hand, Haiku has now tutorials on developing applications, developers/user conferences.....will it now go in hyperbolic development? Sincerely hope so (and best wishes to them).

Reply Parent Score: 3

RE[2]: Not bad..
by vodoomoth on Fri 20th Aug 2010 15:35 in reply to "RE: Not bad.."
vodoomoth Member since:

On the other hand, Haiku has now tutorials on developing applications, developers/user conferences.....will it now go in hyperbolic development? Sincerely hope so (and best wishes to them).

Just to reply on this point, I think one straightforward way to get this hyperbolic development is by opening the flood gates to Java and other virtual machine-based things. The amount of software in Java is just huge. Problem is, the OpenJDK port was announced in January 2008 and still no release date that I know of. The motto should be "reuse as much as possible". In that sense, the FreeBSD networking stack is a good move but the OS needs more of that.

Another way, less easy in my opinion, is the developer momentum. I think Haiku has gained it, at least, they've earned me and I knew strictly nothing about BeOS and Haiku before this year. The general view seems rather favorable as I have never read anything negative about Haiku anywhere on the web, which is a rare fact.

What do you think?

Reply Parent Score: 2

BlueofRainbow Member since:

I have looked at various programming languages available for BeOS/Haiku as I'm not a C/C++ person. The one I would have a preference for (Oberon which was ported to BeOS in the form on an Oberon-to-C translateor) has completely dis-appeared from the Web. So, I may have to become more fluent in C/C++.

There has been a few of Java VM porting projects to BeOS/Haiku over the years. BeKaffe appears to have stalled in 2006. The Sun sanctioned JVM port to BeOS/Haiku (same as the OpenJDK?) appears to have stalled late 2008 when the developer at that time decided to re-prioritize his life.

Perl and Python have been ported to Haiku and this suggests that porting a language is technically feasible.

The Java VM in it-self likely brings a higher level of complexity in the porting exercise in relation to API. The security model inherent to the Java VM may also impede porting to the BeOS/Haiku API which is described as weak in this area.

The "code once and reuse many times" concept allowed by a VM is attractive. However, would this allow access to all the distinctive features of the native API? Probably not.

It looks like experimenting will be the only way to find-out.

Reply Parent Score: 2