In the browser, applications can run compute expensive tasks faster with WASM. For example, decryption of compressed 3D models (https://google.github.io/draco/

In the browser, applications can run compute expensive tasks faster with WASM. For example, decryption of compressed 3D models (https://google.github.io/draco/ https://google.github.io/draco/). AFAIK Figma uses WASM for some expensive calculations. If there is already C/C++ code, it is especially useful. However, as Javascript is already really fast, for most use cases the overhead doesn´t pay off. WASM in the browser did not take off as expected by many. WASM on the server is interesting for companies providing compute services like edge computing or traditional FAAS like AWS Lambda. As WASM has very good security features (sandboxed) it is much cheaper to provide a secure edge compute service for WASM only than one that supports Java, .NET, Node, Python, Go, ... However, neither the enduser nor the developer are the winner here. For most languages WASM is slower. For developers it is obviously easier to provide just your .NET code to the cloud provider than to compile it to WASM. Most (if not all) cloud providers also support NodeJS, so if you would need to develop an edge function I'd highly suggest just writing it in Typescript. So, WASM can help cloud providers make even more money or for very demanding web applications. Otherwise, a lot of hype ...