Some thoughts on Go and Erlang
I write it fully acknowledging that programming language flamewars are pointless, but this article just shows that you don't even have to try hard to create a biased comparison.Here's the essential difference between Go and Erlang: Go gets most of the things right, Erlang gets way too much wrong.So what does Go gets right but Erlang doesn't:* Go is fast. Erlang isn't* Go has a non-surprising, mainstream syntax. You can pick it up in hours. Erlang - not so much.* Go has a great, consistent, modern, bug-free standard library. Erlang - not so much.* Go is good at strings. Erlang - not so much.* Go has the obvious data structures: structs and hash tables. Erlang - no.* Go is a general purpose language. Erlang was designed for a specific notion of fault tolerance - one that isn't actually needed or useful for 90% of the software but every program has to pay the costs* Go has shared memory. Yes, that's a feature. It allows things to go fast. Purity of not sharing state between threads sounds good in theory until you need concurrency and get bitten by the cost of awkwardness of having to copy values between concurrent processesSo sure, if you ignore all the major faults of Erlang (http://damienkatz.net/2008/03/what_sucks_abou.html, http://www.unlimitednovelty.com/2011/07/trouble-with-erlang-..., http://ferd.ca/an-open-letter-to-the-erlang-beginner-or-onlo..., http://sacharya.com/tag/erlang-sucks/) it compares very favorably to Go.You just have to overlook ugly syntax, lack of string type, lack of structs, lack of hash tables, slow execution time. Other than those fundamental things, Erlang is great.