Linked by Thom Holwerda on Fri 28th Oct 2005 11:17 UTC
Thread beginning with comment 52602
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/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
Herb is spot on. You'd expect him to be, as he is an engineer of such proven standing.
Most apps are single-threaded. But then again the whole word 'app' is about user-interaction.
Demanding computing (scientific, graphics e.g. rendering movie special effects) has gone parallel whereever possible. But that is hardly your desktop 'app'.
So many apps are annoyingly single-threaded. Microsoft Outlook and Lotus Notes (from personal experience) both 'hang' while doing searches, but interestingly not when doing 'advanced searches'. I have yet to understand why the developers took this shortcut, as any reasonable beta-tester would run into it and complain.
In Java, many basic containers (e.g. Vector) are thread-safe by default. People don't realise it is a powerformance cost they have been bearing. It will all be worth it. Lets hope that Herb takes the frameworks a lot further, so that a 'modern' program can be more easily parallelised (preferrably by compiler, but compilers cannot easily refactor your basic algorithm choices, mores the pity).