Disclaimer The original post was written by Andrew Gerrand on 13 July, 2010. I’m reposting it not because it’s “absolutely” correct, it just offers another perspective of concurrent programming, and in SOME case, it might be more suitable than “sharing memory” or “mutex stuff”. It may also help you appreciate some design philosophy of Go, and provide you with some inspiration when dealing with concurrency or other problems. Again I’m not saying it’s BETTER, it’s just another another way of thinking and designing. ...