"Asynchronious message passing is old and great idea. Instead of synchronizing objects and dealing with deadlocks we try to isolate objects and let them exchang

"Asynchronious message passing is old and great idea. Instead of synchronizing objects and dealing with deadlocks we try to isolate objects and let them exchange messages. Erlang proved it to be extremly powerful tool applicable to wide range of highly scalable mission critical applications. In JVM landscape big interest to this approach started after introducing Scala actors. " That statement is so very poorly informed! JMS ("surprise"?) has been a sign of "interest" in "Asynchronious message passing" in the "JVM landscape". I am not up on my Scala, but the author fails to convey (based on what I do know ;) the competence level that would lend weight to his attempt to address (much less support) the topic. For those interested in other JVM alternatives, Kilim seems quite promising and seems to hold its own quite well in benchmarks against Erlang. http://www.malhar.net/sriram/kilim/ http://www.malhar.net/sriram/kilim/ http://www.youtube.com/watch?v=37NaHRE0Sqw http://www.youtube.com/watch?v=37NaHRE0Sqw http://sujitpal.blogspot.com/2009/01/more-java-actor-frameworks-compared.html http://sujitpal.blogspot.com/2009/01/more-java-actor-framewo... [scroll to end to see the impressive results for Kilim.] http://osl.cs.uiuc.edu/docs/pppj09/paper.pdf http://osl.cs.uiuc.edu/docs/pppj09/paper.pdf [edit: added pdf link]