2 ms·
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
by Millennium 10y ago
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).
- sp332 10y agoasm.js can interpret wasm as a fallback, but once wasm gets built-in to browsers, it won't be JS anymore.
- bobajeff 10y agoI'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.
- binji 10y agoI've made some progress on this, but there's still a way to go: https://github.com/WebAssembly/sexpr-wasm-prototype/commit/833daf9460887289d2d37ba16da56b5cda5a64af https://github.com/WebAssembly/sexpr-wasm-prototype/commit/8...