I think you can summarize the go flavour of "readability" as: Fewer constructs for the price of higher Signal-to-Noise ratio. Go eschews almost any kind of sy

I think you can summarize the go flavour of "readability" as: Fewer constructs for the price of higher Signal-to-Noise ratio. Go eschews almost any kind of syntactic sugar that might be unfamiliar to you. The endemic "if err != return err" issue is also highly indicative of this choice. I really find that quite hard to stomach. For small apps, this can be acceptable, but for any Go app that gets large enough, this trade-off becomes untenable. You have to scan through too much visual noise to get a clear understanding what the code is doing.