Linked by Thom Holwerda on Sun 9th Sep 2007 18:08 UTC, submitted by koki
Permalink for comment 269946
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:
2005-07-06
I don't agree. The problem is that a lot of developers just won't or will not understand multi-threading. Using a language that "hides" the locking & message passing details may help mitigate that problem somewhat, but they'll still have very little idea of how it works.
Writing multi-threaded C++ is easy. There are three or four rules to remember and that's about it. Any developer should be capable of it.