The difference lately is the number of tools that are now in place for WebAssembly development and the new extensions to WebAssembly (WasmGC, Memory64, etc.).

Despite 28 years of effort at optimization, JavaScript is outperformed by WebAssembly. There's not much coming back from that:

https://jordaneldredge.com/blog/speeding-up-winamps-music-vi...

https://www.amazon.science/blog/how-prime-video-updates-its-...

https://web.dev/case-studies/google-sheets-wasmgc

▲

liontwist a year ago | parent | next [-]

?? JavaScript was outperformed by every language since it was introduced.

It doesn’t matter. What matters is what people put in their web pages.

▲

peutetre a year ago | parent [-]

But now JavaScript is no longer the privileged language in the browser.

With WebAssembly every language runs in the browser and runs better.

	▲	liontwist a year ago \| parent [-]
		And what will prove that is adoption. As others have said, that has been “just around the corner” for years.

▲

yoelhacks a year ago | parent | prev [-]

Javascript is outperformed by WebAssembly in the sense that it runs faster.

A lot of things that bring a lot of value to a lot of people are still much, much faster to build via the JS / TS ecosystem.

It absolutely makes sense that calculation-heavy workloads will be ported to WASM, but there's a lot more to building an app.

	▲	peutetre a year ago \| parent [-]
		> but there's a lot more to building an app. Like what? Visual UI designers? WebAssembly's got you covered: https://platform.uno/blog/uno-platform-studio-featuring-hot-... Running Visual Basic in a C# application compiled to WebAssembly? Sure, why not: https://bandysc.github.io/AvaloniaVisualBasic6/