Linked by Thom Holwerda on Wed 18th Aug 2010 21:02 UTC, submitted by koki
Permalink for comment 437627
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
Features
Linked by Thom Holwerda on 05/24/13 17:26 UTC
Linked by Thom Holwerda on 05/21/13 21:38 UTC
Linked by Thom Holwerda on 05/20/13 11:29 UTC
Linked by Thom Holwerda on 05/18/13 21:33 UTC
Linked by David Adams on 05/16/13 4:23 UTC
Linked by Thom Holwerda on 05/11/13 21:41 UTC
Linked by Thom Holwerda on 05/08/13 14:22 UTC
Linked by Thom Holwerda on 05/02/13 15:28 UTC
Linked by Thom Holwerda on 04/29/13 21:06 UTC
Linked by Thom Holwerda on 04/24/13 22:24 UTC
More Features »
Sponsored Links



Member since:
2009-01-06
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.