But those are far better topics for a discussion about idiomatic Go. I would rather see how to deal with lack of custom default values or error handling rather than how many spaces one should place after a punctuation mark.
That seems to be the exact context where we should be talking about idiomatic Go. You expect feature X and you are unhappy that Go doesn't have it because it's now harder to do Y. So here is an idiomatic Go way to do Y. Or that's why you should do Z in Go instead.
