WasmAssembly

Join WasmAssembly host Thomas Steiner for a deep dive into the world of Kotlin/Wasm with Zalim Bashorov from JetBrains! This episode of WasmAssembly explores how Kotlin, known for being concise, multiplatform, and fun, became the recommended language for Android, and why JetBrains decided to expand its reach to WebAssembly. They discuss how people are currently using Kotlin on the Web, the power of Kotlin Multiplatform, and the future of Kotlin/Wasm, covering exciting recent and new proposals like Garbage Collection, Exception Handling, and Shared-Everything Threads. Tune in to hear about the tooling, next milestones, and the evolving landscape of Kotlin development.

Chapters: 0:00 - Introducing Zalim from JetBrains 2:19 - Kotlin: Concise. Multiplatform. Fun. But what does this mean? 9:05 - How did Kotlin become the recommended programming language for Android? 16:17 - Why did JetBrains decide to support WebAssembly? 25:36 - People use Kotlin on the Web, but how? 31:15 - What is Kotlin Multiplatform? 37:48 - Understanding canvas-rendered apps 41:17 - Could the HTML-in-Canvas proposal help? 43:59 - New Wasm proposals Zalim is excited about 54:29 - What about Kotlin on the server? Resources:

Get ready for WasmAssembly episode 16! Host Thomas Steiner sits down with Patrick Dubroy and Mariano Guerra, authors of the ebook "WebAssembly from the Ground Up." Discover how they're teaching Wasm by building a compiler in JavaScript, why writing WebAssembly by hand is crucial, and their thoughts on the future of compiler education. Tune in to learn about Ohm, the surprising omission of WAT, and what a potential part 2 of their book might cover!

Chapters: 0:00 - Welcoming Patrick and Mariano, authors of "WebAssembly from the Ground Up 1:34 - How the book came to be 5:34 - How the co-authors met 9:13 - Who should learn WebAssembly by actually writing it? 13:13 - Is it time to retire the Dragon Book? 17:42 - What is Ohm, what it has to do with the programming language Wafer, and why they chose Ohm for the book 27:22 - Compiling Ohm grammars to Wasm 30:22 - The on-purpose omission of the Wasm text format WAT 38:27 - A potential part 2 of the book 43:36 - The biggest surprise when writing the book 50:42 - Wasm, but not

Resources:

In this episode of WasmAssembly, host Thomas Steiner welcomes Thomas Lively from Google, the new co-chair of the W3C WebAssembly Community Group. Taking over the role from past guest Deepti Gandluri (episode #2), we seize the opportunity to ask Lively the exact same three questions we posed to Deepti—listen back to compare their perspectives! In the second half, the two Thomases dive deep into the proposals Lively is personally championing, covering Custom Descriptors and JS Interop, and the highly-anticipated Shared-Everything Threads.

Chapters:

0:00 - The Wasm team "Thomas" confusion

0:57 - Thomas' way into Google's Wasm team

4:10 - Wasm CG vs. Wasm WG

9:39 - Is Wasm standardization moving slowly?

17:58 - Wasm at Google and the Chrome team

22:33 - The Custom Descriptors and JS Interop proposal

35:02 - The Shared-Everything Threads proposal

43:28 - Wasm, but not

Resources:

In this episode of WasmAssembly, your host Thomas Steiner is joined by Ömer Ağacan and Martin Kustermann from the Dart team at Google. They explore Dart, the language behind Flutter, and how Dart nearly landed in V8 alongside JavaScript, and why Flutter doubled down on Dart and WebAssembly Garbage Collection (WasmGC). Ömer and Martin then share insights on Dart's performance leap from dart2js to dart2wasm, its potential beyond the browser, and what the WasmGC transition means for developers and the broader ecosystem. Finally, they look at Jaspr, Dart-only web apps, or how different browsers are handling WasmGC. This episode again is packed with sharp technical detail and bold visions for the future of WebAssembly.

Resources:

On this WasmAssembly podcast episode, host Thomas Steiner speaks with David Kircos from Quadratic. They discuss how Quadratic's spreadsheet utilizes WebAssembly to enable scientific computing directly in the browser, leveraging tools like Pyodide, pandas, and numpy. The conversation also covers practical challenges such as bundling large-scale Wasm applications, exploring browser limitations, and Quadratic's integration of AI.

Resources: