True enough.  But it's certainly more natural to think about than mutex-based 
concurrency, automatic parallelization, etc.  In the long term there may turn 
out to be better models, but I don't know of one today.

Also, there are other goals for such a design than increasing computation 
speed: decreased maintenance cost, system reliability, etc.  Erlang processes 
are equivalent to objects in C++ or Java with the added benefit of asynchronous 
execution in instances where an immediate response (ie. RPC) is not required.  
Performance gain is a direct function of how often this is true.  But even 
where it's not, the other benefits exist.


I like that description!

Casey

Reply via email to