4 ms·
You can bridge it though. See https://github.com/rust-webplatform/rust-todomvc https://github.com/rust-webplatform/rust-todomvc , rendered at http://rust-webpla
by 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 agoIts 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 agoI’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.