Linked by Eugenia Loli on Wed 23rd Jan 2008 22:05 UTC, submitted by koki
Permalink for comment 297550
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2006-03-16
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