Updating the Go Memory Model
> In other words, Go encourages avoiding subtle bugs by avoiding subtle code.<p>I find this philosophy strange when they talk about the communication primitives. Channels are <i>extremely</i> subtle in my experience. A channel can be buffered or unbuffered, it can be closed, and there’s different behavior of read/write whether it’s in a select or not. And then you often end up with multiple channels as well. Reviewing code with channels is often more confusing than code that uses mutexes in my opinion.