In this episode, Thomas Steiner interviews Mozilla’s Ryan Hunt, who’s the champion of the string built-ins proposal. They first discuss Ryan’s way into Mozilla and his role in the SpiderMonkey team, and then dive deep into the string built-ins proposal and some challenges and rabbit holes with it. Chapters: 0:00 - Introduction 0:55 - The SpiderMonkey team at Mozilla 5:01 - Ryan’s most exciting WasmGC app 7:32 - Ryan’s way into the WebAssembly world 11:12 - What are string built-ins 16:56 - The confusing concept of strings 20:32 - Calling into JavaScript from WasmAssembly 22:53 - The next built-in candidate 25:02 - String built-in and a language’s native implementation of strings 26:53 - JavaScript glue code 34:26 - The challenges with ‘this; and operators like `===` 38:06 - Actually using string built-ins 42:28 - Runtimes without a JavaScript engine and polyfilling 45:04 - Why’s Mozilla championing string built-ins 49:03 - The compact imports proposal 50:11 - Can we soft-cut the cough? Not a big deal if not. 54:15 - The memory 65 proposal 56:03 - Wasm, but not Resources: Ryan Hunt on LinkedIn → SpiderMonkey blog → WasmGC proposal → Google Sheets WasmGC → BrowserTech podcast episode with Row Zero → String Built-ins proposal → Potential other built-ins → Lin Clark’s post on calls between JavaScript and WebAssembly being finally fast → The problems with `this` and operators like `===` → Using built-ins → Polyfilling built-ins → Scheme Wasm compiler → OCaml compiler → Compact impact section proposal → Compact impact section slides → Memory64 proposal → Seinfeld → Frasier → Scrubs → Culver’s restaurants → Menards home improvement store → Ryan on GitHub → Watch more WasmAssembly → Subscribe to Chrome for Developers → #WebAssembly #Wasm #Strings #StringBuiltins #Standardization Speaker: Thomas Steiner
Hide player controls
Hide resume playing