Lift your state up to the URL. When to do it, how to do it and what's the new best way to do it.

Internationalization in JavaScript and on the web platform is very complicated, but also vastly important for us developers in order to build accessible and intelligible interfaces. Thankfully, Unicode Consortium's MessageFormat working group and TC39 have been hard at work standardizing the next generation of i18n tooling that aims to unify analogous non-standard tools in use today while approaching this problem from a fresh perspective.

Join me along this tour of i18n in JavaScript, discover some of the newest additions to the toolkit and learn about the ongoing MessageFormat proposal and how it aims to radically improve the developer experience.

Client-side navigation has always been the SPA advantage over server-rendered apps - click a link, see the next page instantly, no round trip. Next.js has been closing that gap piece by piece, and its latest rendering model gets it most of the way there without giving up streaming, caching, or Server Components. This talk breaks down how Next.js decides what's static and what's dynamic at the component level rather than the route level, why that shift is what actually makes instant navigation possible, and what's involved in bringing it into an existing production app.

Back in the 2000s, browsers shipped once a year: with cake, fireworks, and a press tour. In the 2010s, releases jumped to 6–8 a year. In the 2020s we’re already looking at a dozen a year, and by the end of 2026 most browsers will start shipping every two weeks. Even if you’re a 10x god with a herd of LLM agents at your back, their models were trained six months ago, and they’re often simply out of the loop, and they'll lie to your face with a smile. What's already possible, what still isn't, and how to actually stay on top of everything happening on the web platform.