What We Got Right, What We Got Wrong
summary
Fourteen years after Go’s launch, the talk lists concrete wins — a formal spec enabling multiple compilers, trivial cross‑compilation, a strong compatibility guarantee, a large standard library and fast tooling including gofmt/go command and integrated testing — and clear mistakes: slow community package management rollout, poor early docs (missing runnable examples), a long road to generics solved by generics via type sets, and confusion between concurrency and parallelism that caused surprising slowdowns.
AI-written summary · about
chapters (15)
- 0:00Intro
- 4:47The Gopher
- 7:22Specification
- 11:30Concurrency
- 16:41Interfaces
- 21:20Compilers
- 24:07Project Management
- 26:53Package Management
- 28:39Documentation
- 29:55Conclusion
- 31:37Questions
- 35:22Future of Gopher
- 40:24Compiler safety
- 42:10Personal regrets
- 43:48Arenas
