Benchmarks indicate as such:

> Wasm is 1.95-11.71x faster than JavaScript on Firefox

> Wasm is 1.15-1.67x faster than JavaScript on Google Chrome

> Wasm is 1.02-1.38x faster than JavaScript on Safari on

https://www.adservio.fr/post/how-fast-and-efficient-is-wasm

That's all a bit beside the point. VSCode is written in TypeScript, and there's no easy way to compile TypeScript to Wasm as it is designed to rely on a full JavaScript runtime.

But VS Code is already JavaScript, running it in a WASM-based JS interpreter instead of a native JS interpreter would just slow things down.

Your benchmarks are analogous to Toyota on highway 0-60 8sec Porche on highway 0-60 3sec But Tell me how they perform with load, bumpy terrain, tyre wear. Just because something runs faster on WASM doesnt mean u have to use it, there are othet things to consider to see if its even worth it. Vscode is based on mono and is written on top of JS/TS. Why woukd you compile it to something and run it on top of WASM, rather than just running it using the native browser engine.