Are We Enterprise-Ready Yet?
summary
Claim: server-side Wasm is promising but not turnkey — compiling existing code is often painful, no stable WASI for containers, and debugging is weak (DWARF draft exists but tooling lags). Tools and products mentioned include Wizer and Chikory, Spin/Cosmonic/XISM and XTP; some deployments work (C Ruby parser, Python UDFs, message-queue transforms in Go) while observability usually stops at the module border and supply-chain/productization forces rebuilding and provenance hunting for every Wasm-bearing npm package.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:05Defining enterprise in WebAssembly
- 2:52WebAssembly for startups
- 6:47End-user experience with WebAssembly
- 9:15WebAssembly adoption challenges
- 13:12Corporate adoption hurdles
- 19:32Debugging WebAssembly
- 22:43Security in enterprise WebAssembly
- 26:35WebAssembly value despite challenges
- 28:00Enterprise-ready software criteria
- 29:47Q&A
related talks
20mAnswering the call: taking WASM seriously
31mHow We Can Create a Thriving Wasm Ecosystem
15mClosing Remarks
35mMicroservices and WASM, Are We There Yet?
33mWebAssembly: The Next Frontier of Cloud Computing
12mThe Wasm Wilderness: Technological Peaks We've Reached with WebAssembly
30mWASM in the Wild West: A Practical Application Tale
29mNew Adventures for WASM