3 ms·
Currently, WASM calls ultimately execute DOM API commands, so there is no performance benefit for DOM manipulation. This is expected to change, but I don't know
by the__alchemist 5y ago
Currently, WASM calls ultimately execute DOM API commands, so there is no performance benefit for DOM manipulation. This is expected to change, but I don't know the details.
I can't explain why, but WASM files end up much larger than an equivalent JS file. (And often larger than a NPM/framework-based etc JS bundle) Also, a build step.
Perhaps someone else who's used WASM more recently, or used it with a language other than Rust can comment.
It's nice being able to use whichever language you wish, but IMO not worth the downsides in its current state.