WebAssembly is now outperforming containers at the edge
This title could be clearer and more informative.Try out Clickbait Shieldfor free (5 uses left this month).
Luke Wagner of Fastly, speaking at Wasm I/O in Barcelona, outlined the path to WebAssembly Component Model 1.0. The key barrier to mass Wasm adoption is insufficient upstream support in popular languages and frameworks. Preview 3 will extend the component model with async functions, strings, futures, and concurrency primitives. Additional planned improvements include lazy memory allocation, multi-value returns, error context values, and a GC API. The JCO tool currently transpiles components to JavaScript for browser use, while native browser support is being pursued for performance gains. Wagner called on the community to contribute tooling, documentation, and upstream language support to accelerate adoption.
1 Comment
Sort: