WASM is theoretically better for CPU intensive workload. As the article states even for CPU intensive workloads there are still quite a few limitations to take

WASM is theoretically better for CPU intensive workload. As the article states even for CPU intensive workloads there are still quite a few limitations to take into account. What it is good for ATM is IMHO mostly just reusing existing C, rust, whatever (choose your WASM supported language here) code. Practically most web applications are not slow because of CPU bottlenecks but more because of too much communication, large code size etc. WASM at its current state does not seem to have an good answer yet for the code size issue.