JS works with JIT (Just In Time) compilation, meaning every user that requests a web page, will request the JS and your browser will compile that JS on the fly as you request it.

WASM on the other hand is pre-compiled once, by the developer, when he/she is making the code. So when a user requests a WASM binary, they don't have to wait for JIT compilation, since it was already pre-compiled by the developer.

They only have to wait for a tiny piece of JS,
which is still JIT compiled,
a tiny piece of JS to load in the WASM binary.

This saves the user from waiting on JIT compilation and thus speeds up requesting web pages.

WASM also increases security,
since binaries are harder to reverse engineer then plain text JS.

Due to those reasons,
I believe WASM will be the future for Web development.

No clue why people are hating on WASM,
but I guess they just don't grasp all of the above yet.

[–] madkarlsson@beehaw.org 2 points 6 months ago

WASM is great and as it becomes more accessible it will likely take over more and more

OPs meme is just a sign of someone not understanding the softer parts around development. The meme also seems to forget that we tried java in the browser for two decades and it was just... Horrible from all perspectives, in all layers

load more comments (9 replies)