Unfortunately, I think you're serious. And you're probably one of many who think this way. Which shows that people really don't understand what it means to do concurrency (as go doesn't support it really.)
Unfortunately, I think you're serious. And you're probably one of many who think this way. Which shows that people really don't understand what it means to do concurrency (as go does support it, really.)
Comments
Go https://golang.org/
Unfortunately, I think you're serious. And you're probably one of many who think this way. Which shows that people really don't understand what it means to do concurrency (as go doesn't support it really.)
Look the erlang syntax is not that hard.
Unfortunately, I think you're serious. And you're probably one of many who think this way. Which shows that people really don't understand what it means to do concurrency (as go does support it, really.)
Could you explain what Go is missing, then?
These posts cover some of that:
http://blog.erlware.org/some-thoughts-on-go-and-erlang/
http://vagabond.github.io/rants/2015/06/05/a-year-with-go/