GopherCon 2015: Katherine Cox Buday - Simplicity and Go

The mantra of the Go community is “keep it simple”. Sometimes, this idea is distorted to justify poor engineering decisions. In this talk, we’ll explore what simple really means, and what Go brings to the table.

[vladimirbauer]

BTW, she wrote a brilliant book "Concurrency in Go", every Go developer must read.

[curiosull]

Didnt knew about "programming by coincidence", I was calling it "it works by mistake or chance" 😀

[GhthorVX]

I was recently hired as an iOS engineer. For the past 3 weeks I've been wading through objc and swift and at the end of everyday my brain just hurts. Just today I was trying to find some way to write a generic or inheritance solution to avoid copying some method implementations. I wasted 3 hours fiddling around until I let myself drop back to my go roots and just get onward with the real problem at hand.

I miss you go, I promise I'll find my way back to your simple lands and make sweet love to your go routines and channels.

[adicide]

Whaat is this talk even about. it's fun to do PROCEDURAL programming? :D I'm going to work in Go professionally and I really hope it's not the bad and the ugly that folks say it is. This whole argument about large teams using Go rings false. Seems like those use Java and C# mostly, and Go is used for light web services and such. It's quite noisy as well, with these incessant for loops, clumsy error handling and data mutability. Eh, guess we'll see.