Channel
Interviewed Person
Conferences
Watch the keynote from Next.js Conf 2022 live from San Francisco. ◆ http://nextjs.org/13 ◆ https://vercel.com/blog/turbopack ◆ https://vercel.com/blog/vercel-acquires-splitbee
Vercel
Interviewed: Rich Harris
(audience cheering) - Welcome, welcome, welcome to Next.js Conf 2022. I'm excited you could join us today to hear updates across three major areas of web development. It's amazing how much Next.js has grown since our start in 2016 with over 2,400 contributors, over 200 million downloads, and the global community of developers, including those viewing Next.js Conf right now
from London, New York, San Francisco, (audience cheers) and the tens of thousands watching online. The Next.js community is stronger and bolder than ever. Each year, more of the top applications on the web are built with Next.js, particularly in retail, SaaS, media, drawn by its balance between great developer experience and great end user performance.
Next.js had its origins as a React framework for dynamic server under sites. Instead of optimizing for single page applications, we designed Next.js for teams building ambitious, complex applications, but being dynamic has always come with a lot of limits. You've wanted to be dynamic, but it's meant at the expense of costly, always on infrastructure,
requiring manual provision and extensive operations. You've wanted to be dynamic, but it's meant juggling two sets of runtime APIs, no JS in the server and web standard APIs in the browser. You've wanted to be dynamic, but often only in a single region origin, depending on legacy, static, CDN caching to try to perform and scale.
Let that sink in. Unless you were one of the giants of the web, like Google or Facebook.com, the only way to scale a dynamic global application was to downgrade a static. The downsides of static become apparent when faced with dynamic requirements. Your cached or static generated page is at odds with granular user personalization, experimentation, or even showing the number of items
in a shopping cart, so you turn to shipping massive amounts of client-side JavaScript. We knew that the answer was never in optimizing within those constraints. We're ready for a new paradigm. Today, we're releasing Next.js 13 to enable you to be dynamic without limits. Next.js 13 ships innovations across three major categories.
First, compiler infrastructure. Originally, way back in my day, we built Next.js on top of Webpack, an open source bundler that revolutionized front end development. While Webpack has allowed JavaScript to go from sprinkling interactivity on a page to building entire web applications with just JS or TypeScript, it's time for a major upgrade,
the successor to Webpack. Second, routing and rendering infrastructure. We'll introduce a redesigned approach to layouts, data fetching, and server rendering. Building on React's multi-year investments, we're delivering on the dream of shipping dramatically less client side JavaScript, while making the most ambitious applications, not just possible but easy. Everything you love about React and Next.js,