10 ms·

Not exactly, WebAssembly has no direct DOM access so if you want have your front end run in WebASM you’ll still need JavaScript to make anything work. Personal

Not exactly, WebAssembly has no direct DOM access so if you want have your front end run in WebASM you’ll still need JavaScript to make anything work. Personally I think that’s a good thing, I don’t want front ends to get any more obfuscated than they have gotten.

ozten 9y ago
Not really, minimal bridge only has to be written once and is reusable across any language that compiles to Web Assembly.
- tyingq 9y ago
  That minimal bridge is anywhere from 10x to 100x slower than pure JS right now. https://github.com/rust-webplatform/rust-webplatform/issues/20 https://github.com/rust-webplatform/rust-webplatform/issues/...
adamnemecek 9y ago
"Where we're going, we don't need a DOM."
steveklabnik 9y ago
You can bridge it though. See https://github.com/rust-webplatform/rust-todomvc https://github.com/rust-webplatform/rust-todomvc , rendered at http://rust-webplatform.github.io/rust-todomvc/ http://rust-webplatform.github.io/rust-todomvc/ That said, I think there are better opportunities for wasm than trying to oust JavaScript; that's not really a stated goal of the wasm project.
- shams93 9y ago
  Its definitely meant to make javascript more capable. Currently while you can do some things with webaudio for example, with WASM you can use complex DSP, you can also build out valuable audio code that you want to keep locked down in binary format where someone getting your algorithm could do damage to your business but in the case of a webaudio DAW the code can't be run on the server.
  - steveklabnik 9y ago
    I’d argue it’s intended to make the platform more capabale. JS is clearly part of the platform. Really though, the point is that wasm’s goals aren’t somehow eliminating JavaScript, but complimenting it.
    - krapp 9y ago
      >the point is that wasm’s goals aren’t somehow eliminating JavaScript, but complimenting it That may not be the goal of WASM's creators, but it will certainly be the goal of many of its implementers.
- flavio81 9y ago
  >better opportunities for wasm than trying to oust JavaScript; that's not really a stated goal of the wasm project. Yes, that's what the wasm guys say, however, what I think is that it will effectively displace Javascript. Not only that, the labor market implications for the current JS full stack developers and front-end developers will be interesting.
pjmlp 9y ago
Today, canvas and WebGL are enough, we don't need DOM. Tomorrow, DOM access might actually exist.
- rickycook 9y ago
  but then we are kinda back in the realms of flash and why that was all so horrific
  - pjmlp 9y ago
    Yep, welcome to the future. Without having to deal with JavaScript.
  - jlebrech 9y ago
    it was only horrific because it had no ui libraries, also what was horrific is that it was a second class citizen.
jlebrech 9y ago
ditching html and css is not obfuscation :P

ozten 9y ago

Not really, minimal bridge only has to be written once and is reusable across any language that compiles to Web Assembly.

tyingq 9y ago
That minimal bridge is anywhere from 10x to 100x slower than pure JS right now. https://github.com/rust-webplatform/rust-webplatform/issues/20 https://github.com/rust-webplatform/rust-webplatform/issues/...

adamnemecek 9y ago

"Where we're going, we don't need a DOM."

steveklabnik 9y ago

You can bridge it though. See https://github.com/rust-webplatform/rust-todomvc https://github.com/rust-webplatform/rust-todomvc , rendered at http://rust-webplatform.github.io/rust-todomvc/ http://rust-webplatform.github.io/rust-todomvc/ That said, I think there are better opportunities for wasm than trying to oust JavaScript; that's not really a stated goal of the wasm project.

shams93 9y ago
Its definitely meant to make javascript more capable. Currently while you can do some things with webaudio for example, with WASM you can use complex DSP, you can also build out valuable audio code that you want to keep locked down in binary format where someone getting your algorithm could do damage to your business but in the case of a webaudio DAW the code can't be run on the server.
- steveklabnik 9y ago
  I’d argue it’s intended to make the platform more capabale. JS is clearly part of the platform. Really though, the point is that wasm’s goals aren’t somehow eliminating JavaScript, but complimenting it.
  - krapp 9y ago
    >the point is that wasm’s goals aren’t somehow eliminating JavaScript, but complimenting it That may not be the goal of WASM's creators, but it will certainly be the goal of many of its implementers.
flavio81 9y ago
>better opportunities for wasm than trying to oust JavaScript; that's not really a stated goal of the wasm project. Yes, that's what the wasm guys say, however, what I think is that it will effectively displace Javascript. Not only that, the labor market implications for the current JS full stack developers and front-end developers will be interesting.

pjmlp 9y ago

Today, canvas and WebGL are enough, we don't need DOM. Tomorrow, DOM access might actually exist.

rickycook 9y ago
but then we are kinda back in the realms of flash and why that was all so horrific
- pjmlp 9y ago
  Yep, welcome to the future. Without having to deal with JavaScript.
- jlebrech 9y ago
  it was only horrific because it had no ui libraries, also what was horrific is that it was a second class citizen.

jlebrech 9y ago

ditching html and css is not obfuscation :P