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




Member since:
2006-02-19
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.