Michael Galpin has written an interesting post on what he’s calling “the Concurrency Myth.”
The message is being repeated over and over to developers: you have to write concurrent code, and you don’t know how to do it very well. Is this really true, or is it just propaganda?
There is no doubt that the computer that we buy are now multi-core. Clock speeds on these computers have stopped going up. I am writing this blog post on a MacBook Air with a dual-core CPU running at 2.13 GHz. Five years ago I had a laptop with a 2.4 GHz processor. I’m not disputing that multi-core CPUs are the norm now, and I’m not going to hold my breath for a 4 GHz CPU. But what about this claim that it is imperative for developers to learn concurrent programming because of this shift in processors?
Read the Full Story.
