I'm not suddenly re-writing everything in Erlang. I'm not even seriously taking it up, as far as I can tell, just playing around (sometimes I'm not really sure until much later how serious I've been about something). It's nice to check out other languages -- what makes the one you're currently using useful, or elegent, or clunky, or bring up issues you hadn't considered? Basically Erlang prides itself on concurrency:

The world IS concurrent. It IS parallel. Things happen all over the place at the same time. I could not drive my car on the highway if I did not intuitively understand the notion of concurrency; pure message-passing concurrency is what we do all the time. Imagine a group of people. They have no shared state. I have my private memory (in my head) and you have yours. It is NOT shared. We communicate by passing messages (sound and light waves). We update or private state based on the reception of these messages. That’s Concurrency Oriented Programming in a nutshell. As for hiding mutable state in an object: it is exactly this property that make parallelization an almost impossibly difficult problem. What's all this fuss about Erlang?

Learn You Some Erlang which is in the style of Learn You Some Haskell