>As a result, Go is a language with first-class concurrency which one can get a grip of in a weekend Which is a mess. Sending mutable objects over channels is

>As a result, Go is a language with first-class concurrency which one can get a grip of in a weekend Which is a mess. Sending mutable objects over channels is anything but "proven concurrency story". Both Rust and Haskell (and OCaml, if we talk about concurrency and not parallelism) have way better concurrency story than Go. I don't care how fast one could start to write concurrent and parallel code if this code is error prone. The only difference between Rust/Haskell and Go is that the former force you to learn how to write the correct code, while the latter hides the rocks under the water, letting you hit them in production.