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!

A systems-level look at the TypeScript compiler. How it converts a file into something into data, checks the validity of that data and finally creates .js files on the disk.

This talk will be a subset of the attached video.

This talk is going to tell the journey of the integration of TypeScript in Node.js with --experimental-strip-types Main point are: - Why waiting so long - How we revolutionized typescript support without source-maps - Shipping it - Unflagging - Next steps

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.