Linked by Thom Holwerda on Tue 26th Sep 2006 23:14 UTC
Permalink for comment 166090
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-08-21
bogomipz has the answer pretty well nailed. The multi-threaded nature of the windows makes porting apps from "traditional" architectures a pain, but makes your UI feel responsive even when the app is pegging the CPU. The window's threads are also higher priority than most apps, which helps some too.
I just finished multi-threading a linux app and I really missed the BeOS threading API... :-D