AI summary by TwinMind
I'm Coming Around To Go...
Theo - t3․gg
21m 32s
Speaker's Evolution on Go
- Initially not a Go fan, but coming around to its value
- Doesn't enjoy writing Go, but recognizes its industry benefits
- Uses Go-built tools daily: ES Build, Vest, Docker
- Dislikes Go-built tools: Kubernetes, Terraform, GitHub CLI
- Acknowledges Go enables fast development with relatively good runtime performance
Performance Comparison Diagram
- Posted Twitter diagram showing language trade-offs
- Runtime performance: Rust wins due to manual memory management
- Developer velocity: TypeScript fastest for 0-to-1 or 1-to-10 development
- Compilation times: Go "comically faster" than other options
- Rust paradox: Used to build faster JS/TS compilers despite having slowest compiler
- Both Go and Rust being used to rethink JS/TS tooling
Personal Go Experience at Twitch (2017)
- Previously worked on Elixir team (2.5 engineers)
- Built infrastructure for Twitch's marathon content
- Loved functional programming and development speed
- Moved to video infrastructure team using Go
- Hated frontend/JavaScript at the time
- Focused on native apps and backends
- Spent 2 months with Go, was "miserable every second"
- Go didn't make him "feel smart" or "spark joy"
- Missed the craft enjoyment he had with Elixir
Go's Design Philosophy
- Designed to be boring, minimal, repetitive, consistent
- Goal: Code from senior dev (5+ years Go) should look identical to junior dev code
- Strange mental shift: C++-like feel but with garbage collection
- Garbage collectors typically associated with higher-level languages (Java)
- Doesn't fit in any specific category box
Go's Technical Issues (via Faster Than Lime)
Type System Problems
- Quote from OSCON conference: "Why did you choose to ignore any research about type systems since the 1970s?"
- Go's types described as "utter chaos"
- Speaker introduced bugs in production due to type system failures
- Values were knowable but type system couldn't detect them
- Handles errors well but handles empty values poorly
- Failed to strike balance between error handling and type safety
Channel Axioms Issues
- Channels pitched as reason to use Go for concurrency
- Four problematic axioms:
- Send to nil channel blocks forever
- Receive from nil channel blocks forever
- Send to closed channel panics
- Receive from closed channel returns zero value immediately
- Behaviors make no sense according to speaker
- No way to detect if channel is closed when receiving
- Inconsistent with Go's error-handling philosophy
Go Team's Acknowledgment
- Recent presentation acknowledged generic container mistakes
- Defined Maps, slices, arrays, channels without giving programmers access to genericity
- Barrier between language-provided and user-controlled functionality
- Caused issues for many developers
Performance vs Developer Velocity Spectrum
- Spectrum diagram: Performance (left) vs Developer Velocity (right)
- C++: Ultimate performance, poor developer velocity
- JS/TypeScript: Good velocity, poor performance
- Python: Similar velocity to JS/TS, potentially faster
- Rust: High performance but slower development than C++
- Gap exists in middle of spectrum ("Uncanny Valley")
- Technologies at extremes get more attention/hype
Go's Position and Arenas Feature
- Go designed to fill middle ground of spectrum
- Garbage collection causes performance gap vs Rust
- Arenas feature was planned to allow manual memory management for core packages
- Would enable "perfect performance" for file readers, JSON parsers
- Speaker was excited about Arenas pushing Go further toward performance
- Arenas now on hold indefinitely - speaker "heartbroken"
- Go seems content staying in middle position
JavaScript Tooling Evolution
- ES Build created by Evan Wallace (Figma CTO)
- Built in Go for faster TypeScript compilation
- Core piece used by almost every modern JS solution
- Vite uses ES Build in dev, Rollup in production
- ES Build contribution chart shows it's essentially one-man project
- Evan Wallace: 3,800 commits, next contributor: 16 commits
Rust-based JavaScript Compiler Issues
- Ecosystem moving to Rust rewrites instead of building on ES Build
- New tools: SWC, RSPack, Turbo Pack, Rolldown
- Rust-based compilers have slow adoption lifecycles
- SWC hasn't kept up with feature additions
- Turbo Pack "notoriously been a mess," massively descoped
- Projects stuck in "development hell"
- ES Build still has best results despite being Go-based
Speaker's Conclusion and Reflection
- Feels guilt for writing off Go's middle-ground position
- JavaScript compilation doesn't need perfect memory safety
- Doesn't need borrow checker complexity
- Thinks ecosystem would be better centralizing around Go vs Rust
- Admits could be wrong, as with previous Go skepticism
- Has shipped ES Build in production many times
- Never meaningfully shipped Rust alternatives
- Recognizes Go's opportunity in middle ground
- Go less interesting due to not being at extremes
- Realizes didn't give Go proper credit for its position
- Still thinks industry may have screwed up going all-in on Rust
