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.

The JavaScript ecosystem is longing for a standardized tooling. No more plumbing work, no more choice fatigue and no more analysis paralysis. But how would such a tool look like? Together, we have a look at the newly released Vite+ Alpha and see if the new open source CLI can hold up to its promises, covering developer's tooling needs and let them focus on shipping, especially in an agentic age.

If you write JS or TS, probably every tool you use daily is currently being rewritten in Rust.

This has advantages (have you heard that Rust is "blazing fast"?), but also potential downsides.

The evolution of JS from the dark days before async/await was fuelled by tooling written in JS. If our tools migrate to a language we don't know, will we lose the ability to control or customize them?

In this talk, I'll explain how in Oxc (the compiler underlying the next generation of the open source Vite bundler), we're trying to "square the circle" - providing rich customisation via plugins written in JS, but maintaining the exceptional performance of Rust - and take you into the nerdy details of memory layouts, allocators, garbage collection, and the tricks that make it possible to have our Rusty cake and eat it with a JS fork.

The easiest thing to do is often what causes hours of debugging down the line. With LLMs becoming increasingly normalized in the industry, an overreliance on them can allow bugs to slip through the cracks.

In this talk, I'll demonstrate a practical debugging workflow: Debug first. Prompt second. I'll show how browser DevTools reveal what's actually happening faster than any AI can guess.

You'll learn:

• Essential DevTools features that improve your bug-fixing prowess
• When to reach for your browser and when AI can actually help
• The almost forgotten art of breakpoints and strategic console messages

AI in your codebase represents growth, but understanding your runtime state represents mastery. This talk is about balancing both and knowing which tool to reach for first.