This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
Not sure of what "spawn" does, but I guess it will be equivalent to: Although Scala implements the concept of actors, I think Erlang provides better support for low-cost concurrency and recovery. On the other hand, running in the JVM is a big plus and with Terracota you can get almost free clustering. [ August 07, 2008: Message edited by: Gabriel Claramunt ]
Actually,I just found that Scala's event-based actors are threadless. Scala uses a pool of threads to serve all actor requests. If I recall correctly, Erlang does something similar. In event based actors, messages are processed with the "react" keyword instead of "receive", the Actors tutorial explains how to use it Also I found a detailed explanation of what happens behind the curtains in Event-Based Programming without Inversion of Control Seems Scala's actors are almost like Erlang ones [ August 11, 2008: Message edited by: Gabriel Claramunt ]