0plus1 : I'm not claiming anything spectacular. If your javascript engine is using a JIT, then for code properly coded, you can have the same perfs as a native binary, because a jit'ted code page in memory is *directly* executable.
That's why, in various benchmarks, you can have Java code beating C/C++ code, or Python faster than C, for example. A codetree that has just been evaluated by a JIT can be more efficient than compiled-ahead code, with the compiler having no information of the context.
That's also why, on iOS, webapps can't use the various acceleration in Nitro. JITting means that you are flagging some memory page as "executable". That could be a potential security flaw for Apple (not if they properly designed their browser, but they are �ber strict about that kind of things...)