3 ms·
It doesn't. Browsers will have to continue to support javascript indefinitely, simply because doing otherwise would break most of the web. Also, the use cases
by krapp 7y ago
It doesn't. Browsers will have to continue to support javascript indefinitely, simply because doing otherwise would break most of the web.
Also, the use cases for javascript and webassembly don't overlap enough for one to replace the other in most cases. Javascript is a text-based scripting language you can write in any editor (the sprawling morass that is the current js development ecosystem notwithstanding,) but WASM requires knowing another language and having a compile step, which adds friction and complexity. You can't really replace a language with a bytecode.
It may mean that other languages can be deployed in the browser as easily as javascript, which may or may not be good depending on your point of view.
I personally look forward to the day when Hacker News embeds the Arc runtime as WASM and replaces all of their javascript with Arc code.
- bogwog 7y ago> It may mean that other languages can be deployed in the browser as easily as javascript, which may or may not be good depending on your point of view. That's exactly what I hope happens. There are so many good languages out there that having to be stuck with javascript for the modern web is a crime.
- MaxBarraclough 7y agoAlso, WebAssembly doesn't have everything JavaScript has. Garbage collection and support for older browsers, for instance. > WASM requires knowing another language and having a compile step, which adds friction and complexity. You can't really replace a language with a bytecode. I'm not sure that requiring a build step is a real problem, for web 'applications' at least. Plenty of JavaScript frameworks use a build step anyway.