Linked by Thom Holwerda on Sun 9th Sep 2007 18:08 UTC, submitted by koki
BeOS & Derivatives "The primary intention of my previous article was to make it very clear why and when locking is needed in multithreaded applications. In this article, I want to present my experiences in writing a new prototype for a replacement of the document model in WonderBrush and how it is manipulated and rendered asynchronously."
Thread beginning with comment 270021
To view parent comment, click here.
To read all comments associated with this story, please click here.
phoudoin
Member since:
2006-06-09

But I sincerely think that C++ is a very bad choice as a language to write multithreaded applications.

Or whatever non HLL. We got it. Thanks.
Now, whatever the language, designing applications that scale well both on responsivness and computing raw power needs developers used to threading design patterns.
No language will know better than you what and where in your application it matter more to use parallelism and where it make no sense at all and, worst case, could even be counterproductive.

Parallelism doesn't oppose procedural language but sequential programming. Two different things. Some language can have built-in parallelism support, sure. And? Doesn't make any threading design pattern article automatically useless.

Edited 2007-09-10 21:02

Reply Parent Score: 1