GopherCon 2016: Dave Cheney - Dont Just Check Errors Handle Them Gracefully

nice talk 👍

Definitely informative, thanks for sharing. However, at least to me I would argue errors are more of a message, and it feels weird to correspond message strongly with behaviors (e.g. a word doesn't always need to have a behavior). Even in the example of the presentation, I think checking if a message is temporary or not is more of a type or status check than about behaviors.

F*ck yeah, thats what Ive been looking for :D

guys, just add try catch into Go

This starts to remind me of Exceptions, but done manually instead of automatically.

a frog in well is Chinese prob.

I'm sorry but this isn't a very good pattern, or somewhat antiquated with regard to older languages. Just as with concerns of monitoring and logging, error handling can too be subjective. A developer shouldn't be tasked with classifying an error, let alone determine which mechanism to use in conveyance.

this should be part of standard library

I played it at 1.25x just so i do not get bored with slow pace

He is chewing it so sloooooooowly

Very practical. Where did you put your library?

Very good pacing on this presentation. I was able to follow along and really absorb what he was saying.