CG, WG, W3C, DeeptiWasm standardization with Deepti Gandluri (Дата оригинальной публикации: )

In this episode, Tom interviews Deepti Gandluri, the Chair of the WebAssembly Community Group at the W3C. You will hear about the difference between the W3C WebAssembly Community Group and Working Group, how Wasm is standardized, how Deepti got into WebAssembly, and the challenges the WebAssembly team at Google faces being part of the Chrome team. Deepti also discusses her favorite Wasm features, how the Community Group might react to a browser-specific proposal, how WASI might work given browser security constraints, and new Wasm features she’s excited about in the context of AI. Chapters: 0:00 - Introducing Deepti 2:44 - WebAssembly Community Group vs. WebAssembly Working Group 8:15 - The WebAssembly phases/stages process 12:39 - Is Wasm’s standardization more about the “how” than the “why”? 19:38 - Wasm’s standardization run out of the Chrome team 22:13 - Deepti’s favorite abandoned, in-progress, and finished Wasm features 32:07 - Browser-only Wasm features 35:05 - WASI file system and the browser 42:33 - Wasm and AI 53:57 - Wasm, but not Resources: Episode 1 with Alon Zakai → Deepti, Chair of the Community Group: → Deepti, member of the Working Group → WebAssembly Summit opening keynote → WebAssembly Community Group → WebAssembly Working Group → WebAssembly W3C Process GitHub → TC39 process document → File System Access API → Web Serial API → V8 Wasm source code in Chromium → WebAssembly active proposals → WebAssembly inactive proposals → Wasm feature detection proposal → JavaScript promise integration proposal → JavaScript promise integration origin trial proposal → WasmGC proposal → WasmGC → WASI file system → Stringref proposal → Built-in Strings proposal → Deepti’s Google I/O talk → Relaxed SIMD proposal → Half precision (FP16) proposal → Memory64 proposal → #WebAssembly #Wasm #ASMjs #Emscripten #Standards, #Standardization Speaker: Thomas Steiner