Linked by Eugenia Loli on Wed 23rd Jan 2008 22:05 UTC, submitted by koki
BeOS & Derivatives The OpenJDK Porters Group approved by a unanimous vote the proposal submitted by the recently formed Haiku Java Team to port OpenJDK to Haiku. This makes Haiku the first OS platform to be sponsored by the Porters Group, and it means that the port is now officially part of the OpenJDK family of projects endorsed by Sun. The team already has a mailing list and a project home page; a mercurial repository is also on its way. Team lead Bryan Varner gives his latest update here on his blog.
Thread beginning with comment 297534
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: What's thisJava thing?
by fyysik on Thu 24th Jan 2008 10:49 UTC in reply to "What's thisJava thing?"
Member since:

Well. 85% of programmers here I know are Java-programmers.. And looking at open job position I suspect that it is situation for whole programming industry here. In web-centric era lot of things is happening behind your look/scene at servers.

So, it is matter of platform-popularity around programmers, not end-users. My son was active BeOS-user, until he got programmer education and job - and for long time he had hope for BeOS Java port - as it don't matter for Java, as you can guess, which platform to use for development. But then he dropped BeOS fully - not due lack of "end-user" apps. But just because lack of Java.

Reply Parent Score: 5

RE[2]: What's thisJava thing?
by TQH ! on Thu 24th Jan 2008 12:39 in reply to "RE: What's thisJava thing?"
TQH ! Member since:

I'm one too. Java rocks.

Unfortunatly Swing's threading forces everyone to learn threading to write a good app, but most don't. So what users percieve as slow Java is just a messed up GUI where everything is waiting for the GUI-thread.

Luckily the Be API choose a better solution where they actually for most cases implemented this threading for you. This is done by using messaging and a worker thread for each window, in comparison to one worker-thread and incoherent calling/messaging in Swing.

Firefox/Mozilla unfortunatly uses the Swing approach which will guarantee that the GUI will never be as good as it could be.

And to put a band-aid on Java they actually added SwingWorker to the API. Personally I think they should rethink the threading completly.

Edited 2008-01-24 12:44 UTC

Reply Parent Score: 2

RE[3]: What's thisJava thing?
by bryanv on Thu 24th Jan 2008 20:11 in reply to "RE[2]: What's thisJava thing?"
bryanv Member since:

The real problem is that they inherited this functionality from the AWT, which Swing uses for heavy-weight components, and the event dispatch model.

The AWT was written for the lowest common denominator of OS's, which as I'm sure you can imagine, delegates a single event pump for all Windows belonging to a process. I can only speculate as to What kIND Of WeirdoS thought that sort of messaging model was a good idea. :-D

Edited 2008-01-24 20:11 UTC

Reply Parent Score: 2