THE VIDEO SHELF · go concurrency
Google I/O 2012 - Go Concurrency Patterns
Rob Pike's Google I/O 2012 talk shows how goroutines and channels solve tricky concurrency problems with simple Go code. It features a playful goroutine demo with gophers passing messages and a search engine example.
Why HN readers recommended it
The canonical recommendation for learning Go concurrency, praised as entertaining and clarifying when to use channels versus mutexes.
This is a summary from the source dataset, not an endorsement by Hacker News or the video creator.
Video & recommendation details
- Creator / channel
- Google for Developers
- Topic
- go concurrency
- Format
- talk
- Level
- intermediate
- HN recommenders in dataset
- 9
- HN mentions in dataset
- 19
- Recommendation years in dataset
- 2012–2025
These counts and years describe the included Hacker News records; they are not YouTube views or the video’s publication date.
From the original HN conversations
Excerpts from the recorded comments. Follow each source for the full comment and surrounding discussion.
Great talk by Rob Pike: [VIDEO] "Go Concurrency Patterns" with cute little gophers playing Chinese whispers with megaphones
mseepgood on Hacker News · 2012-07
In Having a Go - first time experience with GolangFor those who don't know who Rob Pike is, he's pretty awesome, helped create UTF-8 among other things, and now works on Go. [LINK] He has given some really great Go talks which are available on youtube, about an hour each: Origins of Go Concurrency …
canthonytucci on Hacker News · 2013-09
In Less is exponentially more (2012)In one word: channels. They might be theoretically equivalent to some degree, but in practice they are quite different, and I find reasoning about both concurrency and parallelism using goroutines and channels much more natural. Also see this talk by Rob Pike on the origins …
luriel on Hacker News · 2012-07
In Golang at CloudFlare
Summaries, classifications and recommendation records are from the HackerTube source dataset. Read about this library and its limitations.