I love Go for many reasons, but this part is still itching me: I postulate that this Go idiom is a burden on our mental capacity: if err != nil { return nil } Error handling is at a tension between two different developer needs. On the one hand, error handling is very annoying and distracting when working on a constructively formulated use case. On the other hand, not dealing with it correctly means that the program blows up in unknown ways when errors happen: data may be lost, I/O may be hal...
