I've been following asm.js with interest. It looks very cool, but it appears to be mainly for languages which compile to JS - things like Unreal Engine, where presumably they have lots of C/C++ code, and they want to port that to a browser. The JS code that you tend to get with this kind of conversion naturally ends up looking like assembly, since that's what existing compilers do well. You have basically one giant array representing memory, then a lot of JS code that basically shunts numbers around - just like the real assembly you get after compiling C traditionally. Mozilla have figured out how to optimise this special subset of machine-like JS to be within 2x the speed of real assembly. And the very cool thing is it runs on older browsers without specific support; it's all still standards-compliant Javascript, so any browser can run it, although they may be slower at it.
If this was around when we first started Construct 2, it would definitely have been considered as an option. However we already have tens of thousands of lines of JS code hand-written and hand-optimised. I believe this hand-written code already performs very well. If we wanted to go further and take advantage of asm.js, we would effectively have to rewrite the entire engine in another language which compiles to asm.js. This is too much work to justify for a probably small performance boost, and will probably introduce difficult problems around how to handle existing plugins and behaviors. On top of that most games are still renderer-bottlenecked, even on mobile - so it may not even provide any actual framerate improvement at all for many games. So while it's very cool and I'm going to keep an eye on it, I don't think we'll be using it.