Why We Won’t Be Writing JavaScript in Five Years

Re:Why We Won’t Be Writing JavaScript in Five Years by Gxorgxo on Tuesday September 13, 2016 @04:03PM (#12491722)

If you transpile to ES5 you get code that still has to run in the JS engine. WebAssembly is low-level code that gets executed faster and allows you to build different kinds of abstractions on top of it. It's comparable to sending an executable to the browser, it could have been written in any language.

[ Parent | on HN ]

Re:Why We Won’t Be Writing JavaScript in Five Years by FrancoDiaz on Tuesday September 13, 2016 @06:01PM (#12492632)

Uhmm...yeah, I thought I pretty much said that. My point was from the application developer's perspective, what's the difference? Even now, C++ can be compiled to JS via EMScripten to asm.js.

I don't write "JavaScript" right now. I write Typescript. Most of the front-end ecosystems that I deal with (primarily Aurelia and React) aren't being written in ES5. It's usually ES6/7 and Typescript.

[ Parent | on HN ]

Re:Why We Won’t Be Writing JavaScript in Five Years by gsnedders on Tuesday September 13, 2016 @06:45PM (#12492859)

WebAssembly is still run in the JS engine, though. And especially if we start adding GC support to it, that's not going to change.

[ Parent | on HN ]