AI summary by TwinMind
Rethinking React
Theo - t3․gg
12m 33s
Introduction to React's Evolution
- React changed significantly over last 2 years - old code still works but new paradigm available
- Server components fundamentally change React's operation
- Can be described as "two reacts" - analysis of Dan Abramov's "Two Reacts" blog post
- Praise for react.dev documentation quality and educational materials
Client-Side React: UI = F(State)
- Counter Component Example
- Interactive button with instant feedback on click
- No server delay, no additional data downloads
- Component code runs on user's computer
- Count is client state in computer memory
- Initial rendering: "you clicked zero times" sent as HTML
- Client takes over after initial render
- User Experience Requirements
- Direct manipulation needs instant feedback: dragging sliders, switching tabs, typing, clicking like buttons, swiping cards, hovering menus
- Navigation can tolerate delays (clicking links)
- Physical world analogy: elevator buttons provide instant feedback even if action takes time
- Optimistic UI updates - show state changes before server confirmation
- Technical Constraints
- Low latency interactions require zero network round trips
- State lives on user's computer, so components must run there too
- UI computation must happen where state exists
Server-Side React: UI = F(Data)
- Post Preview Component Example
- Displays blog post metadata including word count (2452 words)
- No network requests to count words
- Uses fs.readFile to access file system
- Uses gray-matter to parse markdown headers
- Calculates word count by splitting content and filtering
- Cannot run on user's device - requires file system access
- Data Processing Capabilities
- Code runs where data exists (developer's computer/server)
- Full access to file system during build process
- Pre-processes data before sending to client
- Client receives only rendered UI elements (divs, sections, links)
- No raw data or processing libraries sent to client
- Build-Time Execution
- Components run during build process
- Timestamp example shows deployment time, not current time
- Static generation approach
- No runtime server interaction possible for build-time components
The Fundamental Conflict
- Two Incompatible Visions
- Client React: UI = F(State) - enables instant interactivity
- Server React: UI = F(Data) - enables data processing components
- Counter component cannot run on server (needs current state)
- Post preview cannot run on client (needs file system access)
- Limitations of Each Approach
- Server-only: Can only render initial state, too slow for state passing
- Client-only: Cannot access server-side data sources
- Build-time limitation: Cannot dynamically generate content post-deployment
The Solution Framework
- Real Formula: UI = F(Data, State)
- Most applications need both data and state
- Current paradigms force choosing one abstraction
- Goal: Handle both cases without separate abstractions
- The Challenge
- How to split F (components) across two programming environments
- Need to combine and nest components from different environments
- Must preserve React's component model benefits
- Question: How should server and client components interoperate?
