Our React Wish List

Episode Summary

Executive Summary: Wes and Scott discuss their React wish list: first-class animation/unmount support, stable Suspense and server-side rendering, file-based components, simpler forms, recommended hooks, better JSX ergonomics, and tooling that reduces boilerplate. They stress these are aspirational and acknowledge React’s flexibility-first philosophy, while noting many desired features already exist in Svelte/Vue or in community plugins.

Main Topics: React flexibility vs. opinionated ergonomics: They frame most requests as tradeoffs: React’s flexibility enables many community solutions, but also creates fragmentation and repetitive boilerplate. Animation and delayed unmounting: A first-class way to delay component unmounts for transitions/animations is a top desire, because current workarounds are awkward and library-specific. Suspense and server-side rendering: They want Suspense released, but suspect React may be rethinking it in light of stronger SSR and hydration needs. JSX and component syntax improvements: They want JSX to align more closely with HTML, with simpler conditional rendering, fragments by default, automatic keys, prop shorthand, and scoped CSS. Forms and input binding: They argue forms remain overly verbose in React and want easier state binding, default prevention shortcuts, and HTML-like input ergonomics. Hooks and shared recommended patterns: They would like official or recommended hooks for common tasks like fetch, timeout, and interval to reduce decision fatigue. Tooling and framework-level conveniences: They ask for better scaffolding, built-in routing convenience, and fewer configuration/import hassles, similar to what Next.js and Svelte-based stacks provide.

Key Arguments: React’s flexibility is both its strength and weakness: it empowers the community, but it also produces too many competing solutions and too much decision fatigue. Animation support should be first-class because delayed unmounting for transitions is common and currently awkward to implement safely. Suspense and SSR should evolve together; the delay in releasing Suspense may indicate React is rethinking server rendering and hydration. Forms are still too verbose in React compared with Vue/Svelte, especially for simple input binding and default-prevention patterns. JSX should feel more like HTML and less like a JavaScript workaround; consistent attribute names and simpler syntax would improve readability. Official guidance or shared hooks for common tasks could reduce fragmentation and improve consistency across React projects. Many desired features already exist in ecosystem tools or other frameworks, but first-class support would reduce boilerplate and improve beginner experience.

Data Points: DevLifts premium plan: $199 - One of the sponsors' paid fitness plans; listeners get 50% off with code syntax. DevLifts discount: 50% off - Syntax listeners receive a discount on DevLifts premium plans using the coupon code syntax. DevLifts free plan cadence: every 4 weeks - Free fit-start workouts are emailed as spreadsheets on a four-week schedule. FreshBooks free trial: 30-day unrestricted free trial - Mentioned in the FreshBooks sponsor segment. React update timing guess: within 6 months - Wes predicts React will announce new SSR-related features within six months. Course launch guess: about a month - Wes says his Gatsby course should be out in roughly a month.

Pivotal Quotes: "flexibility as a strength" — Scott: He explains React’s philosophy: many community options exist because React avoids prescribing one solution. "If you know what the problem is, React, why not fix it for me?" — Scott: He says this while asking for fragments by default and automatic handling of common React errors like sibling wrapping. "I think React is going to announce some stuff for SSR in the next six months." — Wes: He predicts React will prioritize server-side rendering and partial hydration over immediately releasing Suspense.

Implications: The episode suggests React may keep its flexible core while gradually adding more opinionated SSR and ergonomics. For listeners, the immediate path remains ecosystem tools; for the industry, Svelte/Vue continue pressuring React toward simpler built-in defaults.