WebAssembly vs JavaScript
The cluster centers on debates about whether WebAssembly (WASM) will replace JavaScript as the primary web language, its current limitations like lack of DOM access, and its role as a high-performance complement.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Can we admit that we hope wasm kills JavaScript yet?
Once webassembly is widely supported, why would we ever write JavaScript again?
Webassembly is the better thing we will replace JS with as a target language for browsers.
I hope wasm becomes the assembly language of the web, before JavaScript does.
Just like Javascript being dead because of WebAssembly.
No, WebAssembly is not currently a general-purpose replacement for JavaScript. Maybe in the future it will be, but right now WebAssembly doesn’t have any APIs to access the DOM. This makes it only good for quickly doing calculations with numbers or data that can be easily represented as numbers, such as implementing a physics engine for a browser game.
WebAssembly will be supported by all browsers and JS engines, but it's not something you would use as your source code. I think at the moment it's more focused on high-performance use cases, e.g. rewriting a CPU-intensive function in C++, compiling it to WebAssembly, and calling it from your JS code. Or taking an existing C++ codebase and running it on the web without really using the DOM. But in the long run, I think WebAssembly will make it possible to do things like DOM interactions
Forget JS! WebAssembly is coming and you can use nice languages with it, for example C#. and if you need compatibility with older browsers you can still compile WebAssembly to JS and send it to old browsers.
No? WASM doesn't replace JavaScript. Think of it as a high-performance library that JavaScript can make use of.
Javascript exists because you can't run anything else in the browser. wasm allows you tonuse your fav language so I can't see why anyone would use JS once wasm gets DOM access