106 karma · joined December 25, 2012
Author's point was that we should not use "not good" languages for the fear that we might be stuck with them for next 20 years. I'd rather be stuck with a language whose designers are very resistant to change vs one that gets features haphazardly bolted on every few years (PHP comes to mind).
if buf, err := json.Marshal(make(chan int)); err != nil { fmt.Println("Ehh..", err) return }
In this case, buf will not be available outside of the if statement. Go fmt can already leave your insignificant whitespace as is, I just wish it could also leave the if error != nil statement say in one line instead of formatting it to take three.
if err != nil { return err }
Take up 70% of all lines in a function.
Correct me if I'm wrong, but I think the math is wrong. Assume prior for being lonely is 50/50. Now, if 100% of twins reported that they are also lonely, this would be proof that loneliness is genetic. If it was 0%, it would imply some sadistic inverse relationship, but one that'd still be genetic. If it's 50%, the same as the prior, it means no relationship. 48% is pretty close.