Deckweiss@lemmy.world
on 11 Feb 16:13
nextcollapse
To answer the headline question:
because wasm fast
(the rest of the points are debatable)
tomalley8342@lemmy.world
on 11 Feb 18:19
nextcollapse
It’s also a compiled blob, which is wonderful news if you were developing closed source software. You don’t have to work around javascript with pesky obfuscation tricks to protect your intellectual property anymore! ♥️
I can see in-browser games and containerized desktop application benefiting from wasm, but simple ecommerce sites without all the fluff can be just as performant with SSR or a multi-page application. For instance several years ago I built the frontend and middleware for the Hart Tools and Ryobi Tools websites using Nuxt for SSR and Algolia for the search. Images are the majority of CPU and network load and the websites are snappy as a result. Even this tech stack is overkill for what the websites need to do but my point is for general use case this or a similar tech stack won’t benefit from introducing wasm.
threaded - newest
To answer the headline question:
(the rest of the points are debatable)
It’s also a compiled blob, which is wonderful news if you were developing closed source software. You don’t have to work around javascript with pesky obfuscation tricks to protect your intellectual property anymore! ♥️
Every program is “open” source if you know how to use a decompiler.
The image is very high persfonmance <img alt="mangled AI mess" src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F1hxtdm441mmonndxshmx.jpg">
WASM in the browser is cool but I think WASI is going to be the big game charger to come out of WASM
the future of complex web apps*
I can see in-browser games and containerized desktop application benefiting from wasm, but simple ecommerce sites without all the fluff can be just as performant with SSR or a multi-page application. For instance several years ago I built the frontend and middleware for the Hart Tools and Ryobi Tools websites using Nuxt for SSR and Algolia for the search. Images are the majority of CPU and network load and the websites are snappy as a result. Even this tech stack is overkill for what the websites need to do but my point is for general use case this or a similar tech stack won’t benefit from introducing wasm.