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 437641
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

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.

It's still alive. I've asked a few weeks ago how I could contribute and someone on the mailing list pointed me to a Wiki page. Just days before that, I read a post (not necessarily on the mailing list), by someone who seemed (to me) to be one of the current leaders, stating that, contrary to what was commonly thought, the port isn't dead...

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.

I think the point of VMs is to offer a well-defined subset of features (VirtualBox comes to mind). The subset does not have to cover all imaginable features found in the real hardware/OS that's being accessed. The JVM has the JNI, which is a significant asset in terms of extensibility, isn't it?

Reply Parent Score: 1