You have the wrong understanding about wasm. It's absolutely not supposed to be replacing HTML, CSS or JS.

And yes wasm is used wildly. On the web for expensive computation (Google earth, figma, autocad, unity games) or server side for portability and sandboxing (Cloudflare workers, fastly, …)

▲

IshKebab 4 hours ago | parent [-]

It is definitely meant to replace JS in some applications. It isn't quite there yet for normal web pages but it will be eventually. There are a few front-end web frameworks written in Rust that use WASM.

The whole "it's not meant to replace JS" thing was just to reduce pushback from JS devs.

	▲	miki_oomiri an hour ago \| parent \| next [-]
		> The whole "it's not meant to replace JS" thing was just to reduce pushback from JS devs. It was born at the same time as webgl, at the time of Jit optimisation for js engines. As a subset of js first, then as wasm as we know it. It was originally for games and performance on the web. At no point there was a conversation about "replacing js", but more like, "js can't do these stuff. let's have something else".
	▲	an hour ago \| parent \| prev [-]
		[deleted]