WebAssembly Specification Prototype

Re:WebAssembly Specification Prototype by Millennium on Wednesday July 13, 2016 @03:45PM (#12089084)

1 - You could use C# (provided that a compiler exists), but this only gets you the language, not the APIs and libraries commonly used by it. In that sense, it's not much different from using Emscripten (a compiler that goes from other LLVM languages to JavaScript) today. For example, XAML won't work unless someone writes a library to translate it into the browser's usual structures. 2 - It's still JavaScript underneath (more accurately, it's asm.js underneath).

[ Parent | on HN ]

Re:WebAssembly Specification Prototype by sp332 on Wednesday July 13, 2016 @04:10PM (#12089263)

asm.js can interpret wasm as a fallback, but once wasm gets built-in to browsers, it won't be JS anymore.

[ Parent | on HN ]

Re:WebAssembly Specification Prototype by bobajeff on Wednesday July 13, 2016 @05:18PM (#12089741)

I've read somewhere that so far the experiments for having asm.js polyfill webassembly isn't looking too promising anymore. I could be wrong though.

[ Parent | on HN ]

Re:WebAssembly Specification Prototype by binji on Wednesday July 13, 2016 @05:35PM (#12089850)

I've made some progress on this, but there's still a way to go: https://github.com/WebAssembly/sexpr-wasm-prototype/commit/8...

[ Parent | on HN ]