In a section of his post describing "What it all means," Eich said:
Moreover, Eich said, "TraceMonkey advances us toward the Mozilla 2 future where even more Firefox code is written in JS. Firefox gets faster and safer as this process unfolds." Mike Shaver, vice president of engineering at Mozilla, said of the TraceMonkey results:"We have, right now, x86, x86-64, and ARM support in TraceMonkey. This means we are ready for mobile and desktop target platforms out of the box. As the performance keeps going up, people will write and transport code that was -too slow' to run in the browser as JS. This means the web can accommodate workloads that right now require a proprietary plug-in. As we trace more of the DOM and our other native code, we increase the memory-safe code base that must be trusted not to have an exploitable bug. Tracing follows only the hot paths, and builds a trace-tree cache. Cold code never gets traced or JITted, avoiding the memory bloat that whole-method JITs incur. Tracing is mobile-friendly. JS-driven <canvas> rendering, with toolkits, scene graphs, game logic, etc. all in JS, are one wave of the future that is about to crest."