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.

How many times did we read about JavaScript being a bad language, JavaScript being on its way out and that technology X would kill it. In this talk, we will take a look at the lessons learnt from attempts at killing JavaScript. We will start as early as the late 90s where the battle for web-domination was still open. Then we will travel through time to understand the current state of an hypothetical javascript-less web platform.

Run your project without drowning in configuration. For common scenarios, you can do, config-free via simple extensions using node's Customization API (you don't need to know what that is). It can be about as simple as telling node you want to use css modules and tsx: module.register('@nodejs-loaders/css-module')

TC39 is working on two proposals, import defer and export defer, whose goal is to allow developers to extract better performance from native ESM, both in the browser and on the server. Let's go together through how they work, and when and where you'll be able to use them!