AI summary by TwinMind
Angular’s Third Era is…weird
Theo - t3․gg
21m 41s
Angular-Whiz Framework Merger Announcement
- Angular team announced merger with Google's internal framework "Whiz" at NG Conf keynote
- Sarah Drasner tweeted thread revealing the framework consolidation
- Whiz powers Google Search, Workspaces, YouTube, Google Photos, Google Meet, Google Play
- YouTube also uses Polymer - described as "interesting mess"
- Whiz focused on performance, resumability concepts for rich web experiences
- Frameworks historically served different use cases but strengths could be shared
Background on Whiz Framework
- Internal Google framework for 10+ years, not open source
- Tightly coupled to internal Google tech stack
- Hyperfocused on performance above all else
- Malte Ubl (Vercel CTO, former Google) admitted they "misread the market" for demand
- Decided not to open source many years ago
- Can see Whiz in Google Photos source code via JS controller/action attributes
Framework Use Case Evolution
- Angular: More enterprise/business focused UIs, highly interactive
- Whiz: Consumer focused, extremely latency sensitive products
- Lines between UI types started blurring
- Google developers wanted cross-framework features
- Led to question: "Why are we duplicating so much work?"
Signal Primitives Collaboration
- Angular signals development aligned with Whiz's exact same needs
- Shared signal primitives developed collaboratively
- Product team enthusiastic to collaborate on aggressive timeline
- Angular signals currently in production for 100% of YouTube mobile web traffic
YouTube Implementation Details
- Christopher Roko from YouTube presented implementation
- YouTube supports 3 main web platforms:
- Living room (smart TVs, game consoles) - custom in-house browser
- Mobile web for low-cost phones with browser-based OS (emerging markets like India)
- Desktop apps including creator tools
- Each platform handles rendering differently
Technical Requirements & Performance
- Angular signals meet universal browser support requirements
- Only need arrays and closures support
- Bundle size less than half of previous approaches
- Perfect for mobile web users with slow internet connections
- Excel at synthetic benchmarks
YouTube Performance Results
- 35% improvement on interaction latency for living room video tile navigation
- Video player controls achieved smooth 60fps (up from ~25fps)
- Shorts carousel swiping achieved 60fps with lower interaction latency
- "Very little effort" required for improvements
- Meaningfully increased topline metrics: views and watch time
- Performance improvements scalable to large, messy codebases
Platform-Specific Details
- Living room apps run in custom browser, serve as native apps
- Mobile web targets feature phones with KaiOS (forked from Firefox OS)
- KaiOS popular in emerging markets, $20-30 phones with 4G support
- TCL manufacturing involvement noted
- Netflix Wii app supported until 2019 as example of platform consistency challenges
Community Developments
- Brandon Roberts (OpenSauced) leading Angular ecosystem improvements
- Analog JS 1.0 released - Next.js equivalent for Angular with SSR
- New component definition syntax proposals
- Framework merger seen as investment in Angular, not killing it
- More Google products using Angular means more reason for continued investment
Technical Architecture Implications
- Signals create data flow graph separate from UI graph
- Unintuitive behaviors need accounting for in large codebases
- Scalability of signal best practices not yet proven in large projects
- React composability model has proven scalability
- TypeScript compiler often bottleneck in large codebases, not framework itself
