How Vercel thinks about Next.js

What It Covers

Tom Occhino, Vercel's Chief Product Officer and React co-creator, discusses React's origins at Facebook, Next.js evolution, framework-infrastructure integration, and Vercel's approach to open source sustainability.

Key Questions Answered

• •React adoption strategy: Never pushed React aggressively on developers - always positioned as "here's something that solves problems for us, try it if interested" which led to organic, sustainable growth over forced adoption.
• •Framework-infrastructure coupling: Vercel builds Next.js and infrastructure together for cohesion, then creates loose coupling through build output APIs, allowing other frameworks like Svelte to run on Vercel's platform effectively.
• •Developer-user experience alignment: Great developer experience serves exceptional user experience - Facebook's Paper app died despite amazing UX because poor DX meant no developers wanted to contribute, proving both must work together.
• •Next.js caching simplification: New "use cache" API replaces complex configuration like "export const dynamic" and unstable cache APIs, providing simpler mental model for determining static versus dynamic content rendering.
• •In-function concurrency optimization: Vercel achieves 12-47% efficiency gains by sending multiple requests to same VM during idle time (disk IO, network calls, LLM requests), eliminating one-request-one-VM serverless limitation.