What's The Framework of the Future?
summary
Panelists compare concrete features and roadmaps: Rock adds a brownfield flow to import one file to instantiate React Native in iOS/Android, Next.js highlights the stable App Router and work on partial pre-rendering, Redwood emphasizes a server‑first, no‑magic, no type‑gen model, Expo pushes file‑based routing, server actions and one‑click deploys plus Expo Go for prototyping, and Parcel demonstrates how to embed server components into existing apps. Consensus: React Server Components and streaming for LLM tokens are essential, and frameworks ask for better external store / fine‑grain APIs.
AI-written summary · about
chapters (9)
- 0:00Introduction to fight night
- 2:40Framework introductions
- 5:57Convergence of frameworks
- 10:03Web and native integration
- 11:46Role of server components
- 15:03AI in framework development
- 19:58MCP and agentic experiences
- 25:10Local LLM and future vision
- 29:59Wishlist and closing thoughts
related talks
34mWhat's Next? Exploring the future of React
23museFrameworks();
51mDiscussion on React server components
23mThe Dawning of a New Age for Fullstack React
25mFetch Once, Render Everywhere: React Server Components in Expo Router
01h 10mThe Future of Frontend Panel
53mFuture of Frontend Panel
21mFetch Once, Render Everywhere: React Server Components in Expo Router