3 ms·
Most current WebAssembly compilation paths produce asm.js as an intermediate artifact. In the near term, backwards compatibility should be relatively simple: sa
by callahad 10y ago
Most current WebAssembly compilation paths produce asm.js as an intermediate artifact. In the near term, backwards compatibility should be relatively simple: save both and load the asm.js code as a fallback.
- mrec 10y agoOr you can do it on the client side by hooking into the module loader and decompiling the wasm back into asm.js. See for example the https://github.com/lukewagner/polyfill-prototype-1 https://github.com/lukewagner/polyfill-prototype-1 PoC mentioned in the wasm FAQ.