> Are there any examples beating "HTML, CSS, and targeted JS" on typical webpage usecases? No, and you won't find any. That's not the use case for WASM right n

> Are there any examples beating "HTML, CSS, and targeted JS" on typical webpage usecases? No, and you won't find any. That's not the use case for WASM right now. If your JavaScript code's purpose is to manipulate HTML/CSS, then using WASM will likely make it slower and worse. That will change and WASM gains the ability to access the DOM without going through JS, but that requires many other big features like GC and reference types, and given that there's not a lot of people working on these things anymore after the Mozilla implosion, it might take many years still, or even never happen.