React: then & now

December 5, 2024

73 min episode · 2 min read

Tom O'Kino,Kurt Mackey

Episode

73 min

Read time

2 min

AI-Generated Summary

Published Dec 19, 2025

Key Takeaways

✓React Server Components: Move data fetching back to server while keeping client interactivity, eliminating loading spinners and waterfalls by streaming dynamic content into static shells for better user experience.
✓React 19 Actions: Submit forms using new action attribute instead of onClick handlers, automatically managing pending states and async transitions without manual state management or useEffect hooks.
✓React Compiler: Auto-memoizes components without useMemo, useCallback, or React.memo - install as Babel plugin to automatically optimize code performance without developer intervention or manual optimization.
✓Use API: Read context and promises directly in components without nesting restrictions or hook rules - can be called conditionally anywhere in component, not just at top level.
✓Component Architecture: React's component-based approach now dominates all UI frameworks including SwiftUI - focus on high cohesion within components, loose coupling between them through props boundary for maintainable code.

What It Covers

React co-founder Tom Occhino discusses React's origins at Facebook, current evolution with React 19 features including Server Components and compiler, plus Shruti Kapoor explains new developer-facing capabilities.

Key Questions Answered

•React Server Components: Move data fetching back to server while keeping client interactivity, eliminating loading spinners and waterfalls by streaming dynamic content into static shells for better user experience.
•React 19 Actions: Submit forms using new action attribute instead of onClick handlers, automatically managing pending states and async transitions without manual state management or useEffect hooks.
•React Compiler: Auto-memoizes components without useMemo, useCallback, or React.memo - install as Babel plugin to automatically optimize code performance without developer intervention or manual optimization.
•Use API: Read context and promises directly in components without nesting restrictions or hook rules - can be called conditionally anywhere in component, not just at top level.
•Component Architecture: React's component-based approach now dominates all UI frameworks including SwiftUI - focus on high cohesion within components, loose coupling between them through props boundary for maintainable code.

Notable Moment

Tom Occhino reveals React's initial JSConf announcement was panned because they presented the solution first instead of explaining the problems with massive MVC models that nobody wanted to touch.

Know someone who'd find this useful?