If you are attempting to learn about concurrent programming I think using python is you're best bet (initially) because it provides a "low signal to noise" whic

If you are attempting to learn about concurrent programming I think using python is you're best bet (initially) because it provides a "low signal to noise" which best demonstrates some of the common pitfalls concurrent programming promotes as well as some of the solutions. (such as those found in the python wiki) [http://wiki.python.org/moin/Concurrency/Patterns http://wiki.python.org/moin/Concurrency/Patterns]. Understanding the problems then allows you to make a better choice and understand some of the choices made for you by the language designers, such as why does Clojure use STM and promote immutability? Are actors/goroutines/coroutines the same thing? What is so good about this reducers library? etc. etc. Linking the dots and the "ah ha!" moments will help you make your choice and understand more about why the tool might be a greater asset than the other. In short: Understand the problem before solving it. (or use the hammer for nails and screwdriver for screws)