JS Party: JavaScript, CSS, Web Development · Changelog Media

React: then & now

·1 hr 13 min·5 clips

Tom Okino says LLM apps should output dynamic applications, not just text or images, through generative UI.

1. JS Party: JavaScript, CSS, Web Development focuses here on React’s early history and Tom Okino’s view of what comes after React. 2. Tom Okino, a React founding team member at Facebook and chief product officer at Vercel, joins K-Ball and Nick at React Summit. 3. The episode asks how React started, why JSX was controversial, and why server/client boundaries matter now. 4. Tom says Facebook’s ads team was building a client-side MVC system similar to Backbone, Ember, or Angular. 5. He says one engineer saw that the code was hard to maintain, with a thousand-line model that only two people could touch. 6. Tom says Jordan brought an early React prototype to the product infrastructure team, where they gave it five minutes and started doubling down. 7. He describes Bolt, Facebook’s in-house framework, as Backbone-like with a different view layer. 8. Tom says the team’s apps became “pathologically complex,” with massive controllers and models that nobody wanted to touch. 9. He says React’s JSConf debut was criticized for mixing technologies and ignoring the industry’s separation-of-concerns idea. 10. Tom says the team should have started with the problems, and Pete Hunt later did that at JSConf EU. 11. He says the key shift was thinking in components, with the component as the atom instead of the page as the unit. 12. Tom describes the props boundary as the seam that preserved loose coupling while keeping high cohesion inside components. 13. He says React succeeded because it could be adopted incrementally, even one piece of one page at a time. 14. He also points to escape hatches like `find DOM node`, which let teams mix React with existing jQuery-like code. 15. Tom says Facebook never set external React-user goals, and that the adoption features emerged from internal needs rather than a growth strategy. 16. He contrasts React with today’s client-heavy apps, arguing that the server should handle data fetching, secrets, and orchestration. 17. Tom says React Server Components point toward a static shell with dynamic bits streamed in while keeping the interface interactive. 18. He says the same pattern applies to infrastructure at Vercel, where the build output API lets frameworks define deployment details. 19. The tone is technical, reflective, and conversational, with K-Ball and Nick pushing for specifics rather than a formal presentation. 20. Listeners who care about React history, Vercel, and web platform architecture will get the most from this discussion. 21. Listeners looking for light banter or non-technical storytelling may skip it.

As heard by us

A grounded look at how LLM apps may move beyond static output into more dynamic UI.

JS Party treats the LLM application layer as unresolved territory, not a finished pattern. It keeps circling the parts that still matter in practice: component-based development, familiar UI conventions, and the tradeoffs behind generative UI.

Read the full review in PlayNext →

Why you'd press play

Want a grounded take on web frameworks, GenUI, and the AI-shaped app layer?

Read the full recommendation in PlayNext →

Listen to the show on

Apple Podcasts Spotify

Play clips from this episode More from JS Party: JavaScript, CSS, Web Development