There are a few reasoned criticisms from the Erlang camp about Go not copying some bits and pieces from Erlang that might have been worthwhile that are worth reading.
> reasoned criticisms from the Erlang camp about Go not copying some bits and pieces from Erlang that might have been worthwhile that are worth reading.
would you mind pointing those out please ? thank you !
thank you ! spent the last 45 minutes just reading the posts by 'jerf', and as he most humbly points out:
Go advocates desperately, desperately need to avoid the temptation to explain to themselves why Erlang isn't as good, because then they'll fail to learn the lessons that Erlang learned the easy way. There's a lot of ways to improve on Erlang, but let me tell you that despite those opportunities, Erlang as a language is one of the wisest languages around, you do not want to try to exceed it by starting from scratch. Learn from it, please, I want a better Erlang than Erlang, but talking yourself into how Go is already better than Erlang isn't going to get you there.
Here is a rant from me ... there is no effortless way to put mysql results into map [string]interface{} (equivalent to mysql_fetch_assoc) with built in typing. You get []byte and have to cast and scan everything yourself. Also go is hard to serach for in google and google groups where golang nuts are - they are as pleasurable for searching and finding info as a kick in the balls.
Apart from that the language is very solid and has some nice decisions made about it.
