>Even if true, it doesn't help much if you have to marshall through JS for nearly every call. If your particular front end code is dominated by many calls to t

>Even if true, it doesn't help much if you have to marshall through JS for nearly every call. If your particular front end code is dominated by many calls to the DOM, then WASM may be a net performance loss currently, yes. In cases where you are doing something computationally heavy then periodically updating the dom with results, then WASM can be a huge win. In cases where the performance is fine either way, being able to use one language server and client is a huge win. I am already doing useful things with WASM and Rust. It is a very very nice workflow.