Apparently it's already supported everywhere except Chrome:
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).
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).
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
Well, if that's a pain, then 6% is small enough to drop/force to upgrade.