Sam Clegg

This looks like a figma issue rather than an emscripten one. That error message is not coming from emscripten but from (I assume) figma. In general you can't expect to...

asm.js isn't really a thing anymore now the wasm exists. I'm not even sure if modern browser still contains special optimizations for it. The closest thing would be building `-sWASM=0`...

> V8 never did. IIUC that is not true. v8 had a mode where it would use a special optimized path for "use asm" files that used the same path...

We have no plans for bring back asm.js support at this time. Emscripten's support for JS is via that wasm2js tool in binaryen. IIRC, when we developed this tool we...

Its not that asm.js won't run everywhere, is that just that wasm2js doesn't generate it. If there were a very compelling reason it might be possible to update wasm2js to...

> Like I said, some legacy runtimes offer optimizations for ASM.js. Especially for Firefox ESR 52 and earlier, maybe Chrome 49 and earlier too. Those specific browser versions are the...

Sorry, by "users" I meant users of your project/website (TiMidity++). How many people are using use website on Windows XP? Is there some reason why your project in particular needs...

> someone please make a guide on how to setup emscripten to compile to asm.js (even if you'd have to use an outdated version), > although there's little to no...

> For this one, I notice that pure js isn't doing well on a KaiOS device, apparently using actual asm.js on KaiOS it will pre-compile asm.js to native code so...

Thanks for the explanation. If building for real asm.js as opposed to plain js makes that difference then hopefully the old 1.39.20 is up to the job. Please let us...