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.

Oliver is a TC39 Invited Expert and the creator of Porffor – an experimental Ahead-Of-Time (AOT) JavaScript engine that can compile TypeScript to Wasm and native code. It has graduated from being a hobby project to now being a full-time activity.

In this talk, Oliver will show how native TypeScript support in JavaScript engines can present interesting optimization opportunities. Type annotations from TypeScript can act as hints to the AOT compiler to allow optimizations that reduce output size, improve performance, and more!

Silicon Valley is buzzing again. Dozens of nightly AI meetups, packed co-working spaces, and a lot of hype. But the real action isn’t in a postal code. It’s on GitHub.
This talk breaks down why JavaScript is powering the AI boom globally, and why you don’t need a Valley badge to be part of it. Just open an issue and commit.
AI-assisted development is becoming part of modern workflows. The goal isn’t to redefine open source. It’s to make sure that as tools evolve, accountability, transparency, and maintainership stay intact.

Cognitive stress has always been a challenge when dealing with new languages, features and APIs. Oftentimes, we find ourselves experimenting with new features, rather than only reading their documentation. Either with a debugger, a REPL environment, or a thousand console.logs, we explore what these tools do. But what if there was something that will further cut the time between writing code and seeing the result? JS Eval is a tool that achieves exactly this by displaying the evaluation results of your program directly where they come from. Join me as we dive into its plethora of features and how they can help you understand the new tools you encounter!