GopherCon 2014 Inside the Gophers Studio with Blake Mizerany

Channel:Confreaks · Length:48:18 · Published:2014-05-22 · Views:8065

Watch on YouTube

Summary

A GopherCon 2014 session where Blake Mizerany replaced his planned talk with a panel discussion with members of the Go team. It covers Go's design choices and community questions.

Why HN recommends it

HN commenters cite it as a source for what Go team members said about language regrets and Go's adoption.

Here is Andrew Gerrand addressing precisely this point two years ago at GopherCon — HN, 2016

Programming language design · C, C++, Rust, Go & systems languages

On Hacker News

This is a frustrating and overly-exasperated post which reaches conclusions that have always been part of the Go canon. APIs should be designed synchronously, and the callers should orchestrate concurrency if they choose -- yes! Channels are useful in some circumstances, but if you just want to synchronize access to shared memory (like the author's example) then you should just use a mutex -- yes… — sagichmal, 2016-03
Rob Pike mentioned variable declaration when asked at GopherCon what he wished he hadn't done in Go [VIDEO] — xkarga00, 2014-10
I would definitely prefer jmpeax's answer. Although, there was a question/discussion similar to this here: [VIDEO] The gist was that, if the interface and the structs that are supposed to satisfy that interface belong to the same package, and then you want to prevent any outsider from implementing that interface, you can actually include an unexported method: type HtmlStringer interface { ToStrin… — hjr265, 2014-06
One of the Go developers did say that Go has a big following in China in GopherCon 2014, thanks to Windows. [VIDEO] — jackyb, 2014-06

Related videos