What's stopping WebAssembly from effectively replacing JavaScript? (programming.dev)

submitted 1 year ago by popcar2@programming.dev to c/programming@programming.dev

69 comments fedilink hide all child comments

I've been wondering about this for a while and haven't really found a great answer for it. From what I understand, WASM is:

Faster than JavaScript
Has a smaller file size
Can be compiled to from pretty much any programming language
Can be used outside of the browser easier thanks to WASI

So why aren't most websites starting to try replacing (most) JS with WASM now that it's supported by every major browser? The most compelling argument I heard is that WASM can't manipulate the DOM and a lot of people don't want to deal with gluing JS code to it, but aside from that, is there something I'm missing?

you are viewing a single comment's thread
view the rest of the comments

[-] jim_stark@programming.dev 1 points 1 year ago

My bad. I can't find the actually video but there exits a startup that shutdown because Rust/WASM performance wasn't any better on top of that it's was harder to develop with Rust. But as my edit to my previous comment shows things got better for Rust. It's no longer the case.

this post was submitted on 07 Aug 2023

86 points (98.9% liked)

Programming

17314 readers

50 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz