>>11
Yes, is it hard (an absolute term, instead of relative to non-concurrent programming) - not as much as people make it out to be. The myth that concurrent programming is
too hardTM comes from all the
(Windows? is it fair to blame it on windows? probably not) programmers who are so used to thinking non-concurrently that the paradigm shift to concurrent seems overly hard. It's a relative thing, not an absolute thing. Obviously it's
harder because it's more complex (as you said), but how much harder is blown out of proportion because people are taught how to program single-threaded non-concurrent applications
too well before they are taught how to program concurrently.