VoyagerRadio writes "Last week I attended a local technology user group's monthly meeting to learn about a programming language I'm not familiar with, Erlang. Wikipedia currently describes Erlang as "concurrent, garbage-collected programming language", a fact that seemed supported by speaker Bryan Hunter's presentation at the event I attended. Mr. Hunter described the language's strengths in concurrency (specifically, shared memory and message passing), in garbage collection (each process has its own garbage collector), in reductions (which provide you with "crazy performance"), and in distribution (which is built-in). He demonstrated how the language is used to create computing clusters, setting up and connecting nodes and then demonstrating some of their unique communication protocols.
The demo impressed upon me the value of functional programming languages (of which Erlang is a member), but I'm still wondering if I should first master one of the more "popular" languages I've been exploring (such as C) or object-oriented languages (such as C++) before trying to fully wrap my mind around Erlang. One thing I picked up from the presentation is that once you learn Erlang, it may be difficult to wrap your mind around OOP once you've gotten used to programming with Erlang.
Should I, as one of the the more well-known resources on the language (http://learnyousomeerlang.com/) suggests, learn me some Erlang?"
Link to Original Source