The slides (and plenty other Go literature) describe the metrics used to decide Go features in quite a lot of detail. If these metrics are applicable in your context, then Go is more likely to "make your life better" than Haskell.
Can you point out to specific PL research results that Go has outright ignored, rather than decided against for X reasons?
this is a very interesting question, but can it be answered?
I mean, we can say that design by contract (or linq/multiple dispatch/type state/whatever) offers an interesting solution to common problems and was ignored.
Can you point out to specific PL research results that Go has outright ignored, rather than decided against for X reasons?