DOM engine and network lag are a much bigger bottle-neck for most mobile apps; where the lack of Nitro really hurts is <canvas>-based games, and specific CPU-he

DOM engine and network lag are a much bigger bottle-neck for most mobile apps; where the lack of Nitro really hurts is <canvas>-based games, and specific CPU-heavy tasks (real-time photo effects, etc). For simple stuff like string manipulation, non-Nitro JS is still crazy-fast enough to be negligible in most cases. However, I can attest that Javascript/browser memory leakage is a very real problem. It's manageable, but also very easy to screw up.