On Tue, 15 Jul 2008, Zubin Wadia wrote: > Date: Tue, 15 Jul 2008 23:11:16 -0400 > From: Zubin Wadia <[EMAIL PROTECTED]> > Reply-To: [email protected] > To: [email protected] > Subject: Re: [twincling] memory barriers and locking primitives > > Just wanted to elaborate a little on Erlang since it made an appearance and > it is my favorite language of the moment. > > 1. Concurrency is certainly an Erlang feature. However, it is not what makes > it unique. Scala does this too using Actors. And Scala even runs on the JVM > as a first-class language. Haskell also gives you superb concurrent > programming capability. In fact, in Haskell it is absurdly simple to spread > over cores using the Control.Concurrent library. > > 2. 'Shared Nothing' architecture is not a factor of concurrency but really > what allows Erlang to scale exceedingly well. But even this is not what > makes Erlang unique. > > What makes Erlang unique is that resiliency is a first-class citizen. By > resiliency I mean its support for Process Monitoring (If anything collapses, > simply kill it, make a new one, figure out where it left off from the > universal stack and go! Similarly, if you notice something fishy going on > with your code - hot swap it with an update. Again the Erlang stack assists. > > Joe Armstrong's philosophy was simple - large systems screw up. When they > do, give the engineers the maximum possible chance of saving the situation. > That makes Erlang unparalled. > > Cheers, > Zubin. >
Hi Zubin: Please see my February 2008 presentation on Erlang http://www.twincling.org/slides/erlang.pdf thanks Saifi.
