Go: building on the shoulders of giants and stepping on a few toes [video]

It is interesting that neither the talk nor the questions from the audience rise the question of the error handling.<p>In Go returning an error implies that the caller will need to add 3 lines of the source for each call to propagate the error. This is really ugly. Rust managed to reduce that source overhead down to the single extra ? character while keeping all the benefits of explicit error handling. I wish Go gets something similar.

Intersting talk. Here are some other talks about the history and origins of Go:<p>Evolution of Go (Griesemer, GopherCon 2015)<p>Video: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=0ReKdcpNyQg" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=0ReKdcpNyQg</a><p>Slides: <a href="https:&#x2F;&#x2F;talks.golang.org&#x2F;2015&#x2F;gophercon-goevolution.slide" rel="nofollow">https:&#x2F;&#x2F;talks.golang.org&#x2F;2015&#x2F;gophercon-goevolution.slide</a><p>Origins of Go Concurrency (Rob Pike, OSCON 2010)<p>Video: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=3DtUzH3zoFo" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=3DtUzH3zoFo</a><p>Slides: <a href="http:&#x2F;&#x2F;go-lang.cat-v.org&#x2F;talks&#x2F;slides&#x2F;emerging-languages-camp-2010.pdf" rel="nofollow">http:&#x2F;&#x2F;go-lang.cat-v.org&#x2F;talks&#x2F;slides&#x2F;emerging-languages-cam...</a>

Presenter has a great sense of humor. For someone who hadn&#x27;t known much about GO, this was a great overview. Thanks

Obligatory, the take on generics: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=sX8r6zATHGU&amp;t=50m29s" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=sX8r6zATHGU&amp;t=50m29s</a>