3 ms·
This is something that I'm worry about: It forces Emscripten builds to be created differently in the way the build artifacts will be compatible only with that v
by trzeci 5y ago
This is something that I'm worry about: It forces Emscripten builds to be created differently in the way the build artifacts will be compatible only with that version of V8 - in practice it means a dead feature that looks nice, but we can't use for a long long time.
- flohofwoe 5y agoApparently it's already supported everywhere except Chrome: https://webassembly.org/roadmap/ https://webassembly.org/roadmap/ So with Chrome's quick release cycles it's probably not too bad (not sure about the 'branded' mobile browsers on Android though).
- trzeci 5y agoThanks for the correction and for the link! Unfortunately I'm still keeping my worry alive. The reality is that we still can't move fully even to wasm, as ~6% of our players have incompatible browser and we have to support asm.js fallback. My worry is that we end up with fallback cascade: - full featured wasm - wasm - asm.js I'm aware that's the reality of technology under development - and most likely we will just find a solution for that (like secondary build (or link if it's just link time)). It's just too bad we can't easy polyfill new features in old browsers for wasm. Still love WASM <3
- coldtea 5y ago>Unfortunately I'm still keeping my worry alive. The reality is that we still can't move fully even to wasm, as ~6% of our players have incompatible browser and we have to support asm.js fallback Well, if that's a pain, then 6% is small enough to drop/force to upgrade.