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."
Permalink for comment 269952
To read all comments associated with this story, please click here.
tuttle
Member since:
2006-03-01

I don't agree. The problem is that a lot of developers just won't or will not understand multi-threading.


The majority of developers are incapable of writing multithreaded code with fine-grained locking. That is just a fact. So your approach is to tell these people to learn low level multithreading primitives or go to hell. Great way to get new developers for your niche platform.

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.


First of all, scala does not hide the message passing details. It just lets you write a message handler in 1/10th the lines of code compared to C++.

And what is the problem about hiding complexity? Many people use the stl without having the slightest idea about the alorithms used by it. Are you saying that abstraction is bad?

Besides, just because somebody does not get low level threading primitives like semaphores and mutexes does not mean that he is a bad programmer. Maybe he has valuable domain specific knowledge.

And I guess all those people using Erlang to program high performance telecommunications gear must be idiots because they use a language that hides many multithreading problems...

Reply Parent Score: 1