This is interesting and inspiring: more and more people start talking about threading not being a programming model.

Joe Gregorio from Google had a talk at PyCon 2010 on this topic. Watch the video at http://python.mirocommunity.org/video/1600/pycon-2010-threading-is-not-a-

Roberto Ierusalimschy said it in his Stanford University talk: "concurrency should follow the model of communicating processes [instead of threads which were designed as an OS-level construct]". The video is here: http://stanford-online.stanford.edu/courses/ee380/100310-ee380-300.asx

I think we are approaching some critical point after which the multithreading non-model will start disappearing from the application programming landscape. It's really the time for threads to go where they belong: the under-the-hood realm of implementation artefacts, along with garbage collectors and i/o caches.