

WebAssembly in Practice with Brian Carroll
Nov 6, 2023
Richard interviews Brian Carroll, an expert in using WebAssembly in practice. They discuss the benefits and challenges of WebAssembly, its slow adoption, and its potential to replace JavaScript. They also explore the drawbacks of using Electron for app development and the efficiency of web browsers as a software delivery platform. The podcast compares WebAssembly and JavaScript, highlighting when to use each and discussing their advantages and performance differences. Additionally, they delve into the variations in SIMD instructions targeting specific architectures and the limitations of WebAssembly for front-end development. The podcast concludes with speculation about widespread adoption and the potential for WebAssembly to replace JavaScript in building applications.
AI Snips
Chapters
Transcript
Episode notes
WebAssembly's Future Role
- WebAssembly's role as a JavaScript replacement depends on the timeframe and whether the web evolves into separate document and app platforms.
- Currently, web apps are essentially "undocumented" documents, leading to inefficiencies.
Electron's Inefficiency
- Richard Feldman finds Electron objectionable because it "documentifies" and then "undocumentifies" apps, creating unnecessary complexity.
- This process impacts responsiveness and resource usage.
Web's Strength and Weakness
- Richard Feldman believes the web browser is the most efficient software delivery platform due to its ease of access and automatic updates.
- However, its document-centric design creates baggage for app development.