Go Team "Ask Me Anything"
summary
Covers why generics landed now and what actually changed: parser and type checker updates let basic editing work but static analyzers and the ssa package need deeper rewrites, runtime sees almost no generic baggage and reflect reports concrete types, and the team measures success by adoption, new libraries and concrete performance (watch for the concern that generics might be a few percent slower). Also covers the product process (growth from ~12 to 50+), the developer survey with 10,000 responses, and recent security releases.
AI-written summary · about
chapters (21)
- 0:00Intro
- 3:30Whats changed over the years
- 5:30How do you make sure people understand the principles
- 6:30How does a product perspective work
- 8:00Tension between technical and product perspectives
- 9:00User research
- 12:30Generics in tools
- 13:50Are AST packages rewritten
- 14:50Measuring success of generics
- 16:30Developer Survey
- 18:15Error handling idioms
- 20:00Overusing generics
- 23:15Biggest challenge
- 24:30Generics
- 26:00Governance
- 30:50Security
- 32:50Round Table
- 36:05Break
- 37:15What would you get rid of
- 40:00Will there be a GO
- 41:45Anything else
