Linked by Eugenia Loli on Mon 27th Aug 2001 05:22 UTC
Permalink for comment
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/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
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
More News »
Sponsored Links



Multithreading is good. Period. If the OS has bugs in its support for it, that is bad of course; but this is not an argument that MT is bad in itself. The fact that BeOS "forces" it onto the app developers is also a good thing, or all the hordes of new programmers would not have used it. Of course it's harder to use than coding a single-threaded app. It's also probably simpler to code in an unprotected, DOS-like OS where you can just do everything; and I'm sure lots of "hard-core" coders have cursed the fact that they weren't allowed to do direct I/O to hardware when they first coded on a protected OS. The single most annoying thing when I (have to) use Windows is apps that block completely whenever they need to do something. You then can't even move or resize their windows. I'd much rather loose a message or two.