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.

When building interactive features on a webpage, JavaScript is usually the way to go. However, with great JavaScript dependencies comes great website instability. Even a minor undefined element can cause your entire webpage to crash. That’s where going back to the basics comes in. Thanks to modern Web APIs, it’s now possible to reduce JavaScript dependency on a website by swapping out JS components for their native HTML element or CSS feature counterparts. In this talk, we’ll take a look at how to use HTML and CSS to build simpler alternatives to popular JavaScript components such as accordions, modals, scroll transitions, carousels etc We’ll also take a look at the performance and accessibility benefits and real-life applications and use-cases of these components.

Let's be honest, nowadays most of us see an error, copy it into ChatGPT, and hope for the best. I've done it. You've done it. We've all wasted 30 minutes going back and forth with AI when our browser could've shown us the answer in 2 minutes.

This talk is about remembering that our browsers have incredible debugging tools we've forgotten how to use. Through live demos of real bugs, I'll show you how breakpoints, call stacks, and the network tab can solve problems maybe faster than any AI assistant.

You'll learn:

• How to ditch console.log hell and actually watch your code run
• Breakpoint tricks that pause your app so you can inspect what's really happening
• How to read call stacks without your eyes glazing over
• Network tab techniques that expose exactly why your API is misbehaving
• When debugging tools beat AI (and when AI is actually helpful)
 I'm not saying don't use AI—I use it all the time. But there's something powerful about understanding your own code well enough to fix it yourself. Plus, you'll be way faster, and you'll actually learn something instead of just copy-pasting solutions you don't understand.