* Browsers will usually compile wasm into native code, yes. Much like asm.js, but with more consistency. However, they also may not, for example for fast startup they may interpret for a while first.
* There have been discussions of threads and fibers and such, and there are ideas for how to add them to wasm, but nothing is finalized yet. On Thu, Nov 3, 2016 at 5:40 PM, Mark Sibly <[email protected]> wrote: > Thank you, all going now! > > Wasm appears to be *amazing* - here's my first wasm app: > > http://www.monkey-x.com/mak/simplelight_wasm/Simplelight.html > > In terms of download size, the .wasm file is 1.6M, vs 16.6M for .asm.js! > > Source code changes required: 0. > > Some questions: > > * Is it running native code? If not, will it one day? > > * Will wasm support any kind of context switching, eg: fibers? threads? > > Congratulations to everyone involved in this, it's a huge achievement! > > Bye, > Mark > > On Wednesday, November 2, 2016 at 3:41:16 PM UTC+13, Mark Sibly wrote: >> >> Hi, >> >> Ok, got my first wasm app built, but when I tried to visit it via browser >> I get: >> >> Assertion failed: on the web, we need the wasm binary to be preloaded and >> set on Module['wasmBinary']. emcc.py will do that for you when generating >> HTML (but not JS) >> >> Does this mean I need to --preload-file the output file with the .wasm >> extension when linking? >> >> This I can do, but I'm not sure what 'set on Module['wasmBinary]' >> involves. >> >> Bye! >> Mark >> >> -- > You received this message because you are subscribed to the Google Groups > "emscripten-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "emscripten-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
