CG, WG, W3C, Deepti-Wasm 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 → goo.gle/4bpFxwV
Deepti, Chair of the Community Group: → goo.gle/3yBtjmm
Deepti, member of the Working Group → goo.gle/3K8NKJU
WebAssembly Summit opening keynote →goo.gle/3WVyQP7
WebAssembly Community Group → goo.gle/3KaOrCM
WebAssembly Working Group → goo.gle/3VbI48B
WebAssembly W3C Process GitHub → goo.gle/3Kd5p3a
TC39 process document → goo.gle/4bL3fno
File System Access API → goo.gle/3UT5uOE
Web Serial API → goo.gle/3WP92nq
V8 Wasm source code in Chromium → goo.gle/4bNiUTa
WebAssembly active proposals → goo.gle/44TBd72
WebAssembly inactive proposals → goo.gle/4btU6je
Wasm feature detection proposal → goo.gle/3K9E95B
JavaScript promise integration proposal → goo.gle/3yxfkOM
JavaScript promise integration origin trial proposal → goo.gle/4aA8Mff
WasmGC proposal → goo.gle/4asI6gI
WasmGC → goo.gle/3WR7GZw
WASI file system → goo.gle/3ylByD1
Stringref proposal → goo.gle/4awO68b
Built-in Strings proposal → goo.gle/3wJ6Fbg
Deepti's Google I/O talk → goo.gle/4boQOOk
Relaxed SIMD proposal → goo.gle/4bNATss
Half precision (FP16) proposal → goo.gle/3wA9rjd
Memory64 proposal → goo.gle/3wA9rjd
#WebAssembly #Wasm #ASMjs #Emscripten #Standards, #Standardization
Speaker: Thomas Steiner

[@chicoxyzzy]

Thank you Deepti and Thomas!

[@thesynalice]

WASM is developing too slow as if it is being sabotaged by individuals that are heavily invested in JS and don't want any radical changes that WASM brings.
Why doesn't it still have DOM manipulation API (and other stuff)?

[@my2iu]

I think the necessary primitives have been implemented, and it’s up to users to write the bytecode/assembly bridging code for a DOM library. So, some Rust or C++ person would have to make the DOM bindings themselves and release an open source library for others to use.

[@user-ib9ns8wj2h]

onlymenothusbandmuk udherkharak mai varitdharisu muk mur program all murnametkharak nothusbandhorenkalitadabblokedi requestyou

[@ChandeshwarKumarTiwari]

Robotek news

[@my2iu]

They really need to come into the office and record these in a proper studio. I’m finding that the audio quality makes it hard to listen to this video.

[@Dominik-K]

I agree, content was very interesting though