for me, the built in goroutines is what moves the needle. The rest of the stuff is very nice, but built-in concurrency is pretty nice.
Yes I know about Erlang, no I won't touch Erlang again.
Yes I know about Erlang, no I won't touch Erlang again.
Check it out :)
Curious, what makes you say that?
At the time, there was no good binary<->string utf8 libraries, not sure what the state of the art is now.
Static compilation and compilation speed make Go very attractive for large projects.
http://learnyousomeerlang.com/dialyzer
( not sure if Elixir supports it though, but it seems so:
It's just optional, and therefore doesn't get used much on open source projects. So the average quality of code suffers.
Whereas something like Go where extra import are hard errors, making best-practices mandatory keeps code to certain standard and it's zero work to setup.
Haven't heard of mandatory dialyzer type coverage yet. It would be kind of commit hook of sort, still external to the compiler though...
Convention > configuration
The easier it is to get going and contribute, the more people will use it. (Haskell pushed hard on this later on and has really benefited. Node did it early.)