On Sun, May 16, 2010 at 3:19 PM, Fabio Kaminski <fabiokamin...@gmail.com>wrote:

> Sorry about using the list like twitter..
>
> but i thought this is a pretty good "article" about functional programming
> side effects, and why actors are not very good design decision..
>
> Actors not good for concurrency model :
>
> http://pchiusano.blogspot.com/2010/01/actors-are-not-good-concurrency-model.html
>
> just another prove that Rich thoughts are pretty concise ,
> and that all are pretty well materialized in clojure's framework.
>
> what convinced me to embrace clojure, is that it choose to make the right
> thing , instead of the popular one..
>
> as haskell community says wisely : "avoid success at all costs " :)
>
> There's no question in my mind that Rich's thoughts are pretty concise. But
then again, there's no question in my mind that Joe Armstrong's thoughts
aren't also pretty concise. There is no system that can fundamentally
guarantee against programming errors in the single core or multi core case.
Erlang has provided a number of constructs that mitigate against poor
multi-processor programming mistakes, but remember, that's mitigate, not
prevent. The article struck me as a long diatribe on a subject that the
author knows just enough about to believe he's an expert when he's really
just scratching at the surface.

Let me be clear. Actors are a proven model to build good, in fact, excellent
concurrent and high reliability systems. That statement doesn't take
anything away from the advances that clojure is bringing to the state of the
art. For us to believe that clojure is pointing the way to a better solution
doesn't require us to say that actors/Erlang sucks.

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en

Reply via email to