Re:A first look at WebAssembly performance
by vbezhenar on Thursday February 09, 2017 @08:43AM
(#13606804)
> The main benefit of WebAssembly is so that we can write code using our favorite languages
JavaScript is already common format that browser understands and there are implementations for a lot of languages translating them to JavaScript. So WebAssembly definitely is about performance, because using other languages is already solved problem.
Re:A first look at WebAssembly performance
by pmontra on Thursday February 09, 2017 @04:47AM
(#13605753)
Are there DOM bindings for languages other than JavaScript or is WebAssembly only for backend/webservices?
Re:A first look at WebAssembly performance
by Matthias247 on Thursday February 09, 2017 @06:01AM
(#13606054)
As far as I understand you can call JS APIs from WebAssembly, which means you use the already available DOM APIs. I don't know exactly what the calling convention from WASM to JS looks like, but I guess it's specified somewhere.
Re:A first look at WebAssembly performance
by TheCycoONE on Thursday February 09, 2017 @07:10AM
(#13606356)
There are a few, none of them optimal for DOM manipulation yet because they all involve calling javascript. There is plans to add wasm dom hooks eventually. https://kripken.github.io/emscripten-site/docs/porting/conne...
The main benefit of WebAssembly is so that we can write code using our favorite languages (not just javascript!) and compile to a common binary format the browser understands. The objectives of WebAssembly never had anything to do with performance.