86
What's stopping WebAssembly from effectively replacing JavaScript? (programming.dev)
submitted 3 years ago by to c/programming@programming.dev
54 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
[–] 4 points 3 years ago* (last edited 3 years ago) (2 children)

IIRC a startup tried to exactly that... It's wasn't any faster and is actually harder to develop.

EDIT:

Sorry ignore these videos. I don't remember which YouTube video it is. But more importantly Rust + WASM got really better than JS these days.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 5 points 3 years ago (1 child)

    The video is essentially saying the exact opposite of what you are saying. It's showing leptos to be much faster than react and I know primeagen doesn't think rust is harder develop.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 3 years 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.

  • permalink
  • fedilink
  • source
  • parent