7 ms·

"It takes a Lightweight-tasks-with-message-passing approach to concurrency." As someone who really likes Erlang's approach to concurrency, I think it is very c

• jerf 18y ago
  Unless I'm very much mistaken, this does not implement "no shared state between threads/processes/whatever", which I consider a bare-minimum requirement to actually have Erlang. You can try to discipline yourself to use such a philosophy anyhow, but Python is going to be one of the worst places to try that. It is mutable to its core, which is one of the reasons it is cool, but doesn't lend itself to this approach very well.
  • durana 18y ago
    Yeah, what I really meant by my comment was it is cool to see this style of programming (lightweight procs & messaging) becoming easier to do in more mainstream languages. While implementation details differ greatly, I think it still gives a lot of credit to the guys who developed Erlang.
    • ralph 17y ago
      Are you aware that using channels for communication and synchronisation has been prevalent in languages other than Erlang? Occam was one, and Bell Labs, creators of C, Unix, etc., used it in Alef and Limbo amongst others. They all hark back to C.A.R. (Tony) Hoare's CSP. Here's a good overview. http://swtch.com/~rsc/thread/ http://swtch.com/~rsc/thread/