I love Go, but I find the following things contradictory in the design.
"Don't communicate by sharing memory, share memory by communicating" from go proverbs[0].
And in the article, "When you create a goroutine, you're essentially allocating a closure and adding it to a queue in the runtime."
Because of this it becomes very easy to share memory by mistake and you end up with bugs. On the other hand Elixir's design makes this kind of thing very hard to do by mistake.
"Don't communicate by sharing memory, share memory by communicating" from go proverbs[0].
And in the article, "When you create a goroutine, you're essentially allocating a closure and adding it to a queue in the runtime."
Because of this it becomes very easy to share memory by mistake and you end up with bugs. On the other hand Elixir's design makes this kind of thing very hard to do by mistake.
[0] - https://go-proverbs.github.io/