I think there is a big difference between &quot;being good for concurrency&quot; and preventing all concurrent programming problems - concurrency is <i>hard</i> and while go does seem to provide a lot of nice structures to make it more straightforward it can&#x27;t, and doesn&#x27;t appear to claim to, hide all the complexities of concurrency from developers.