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

How Vercel thinks about Next.js

·1 hr 12 min·5 clips

Tom Okino says developer experience and user experience should not be a trade-off.

1. JS Party: JavaScript, CSS, Web Development centers this episode on how Vercel thinks about Next.js and React. 2. Tom Okino appears as chief product officer at Vercel and former VP of engineering frameworks at Facebook, while Jared leads the conversation as host. 3. The episode asks how Vercel can build Next.js around React, managed infrastructure, and self-hosting at the same time. 4. Tom says Vercel does not build Next.js to make money, but to support a managed infrastructure business that funds continued framework work. 5. He compares that model with Facebook's earlier React strategy, where the framework filled in gaps like data fetching, routing, and server rendering. 6. Tom says React's strength at Facebook came from solving both the zero-to-one case and the 10,000-foot scale case. 7. He describes Jordan Walke bringing an early React prototype to him at Facebook, and Tom initially thinking, 'please go away.' 8. Tom says the ads org was too busy for a 'skunk work' framework, so he became an internal advocate through product infrastructure. 9. He says the first public reaction to JSX at JSConf was 'terrible,' because the external audience saw Facebook as challenging established best practices. 10. Tom names Sophie Alpert as the first external contributor, after she started tinkering, improving React's approachability, and answering questions on Stack Overflow. 11. He says React adoption moved from almost nobody in production to about '25 tweets a day' during 2014. 12. Christopher Chadeau's tweet count and suggestion to organize a conference marked the moment React started to feel real inside Facebook. 13. Tom says Facebook never pushed React with a 'you need to try it' pitch, and that low-pressure posture helped adoption. 14. He argues that the credibility of Facebook's production use mattered, but only because React also kept a low barrier to entry. 15. Tom says Next.js lets Vercel build framework and infrastructure in tandem so code can translate into optimized deployment behavior. 16. He says the company is still refining self-hosting, image optimization, and other deployment steps, but the tooling is getting better. 17. Tom's clearest argument is that developer experience should serve user experience, not compete with it. 18. The conversation is a calm, technical interview with a lot of historical recall, product framing, and platform strategy. 19. Best for React developers, framework authors, and Vercel users. 20. Skip if you want pure syntax tutorials or short-form news.

As heard by us

A practical look at the tradeoffs behind Next.js hosting and developer experience.

JS Party centers the hidden work behind cloud hosting and the compromises involved in shipping a demanding Next.js app. Kurt Mackey makes a plain case that the cloud is not magic, that self-hosting can be broken into documented steps, and that Vercel is trying to make hosting…

Read the full review in PlayNext →

Why you'd press play

Hear the thinking behind Vercel's Next.js hosting choices.

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