I'm making the point that you don't need a JIT to get good performance out of compiled PHP. A JIT would be useful, but not required. > If you're a language lik

I'm making the point that you don't need a JIT to get good performance out of compiled PHP. A JIT would be useful, but not required. > If you're a language like PHP where you can't guess if a value is going to be a hash or the number 42 until runtime, JIT techniques are essential to get any reasonable performance. Not true, according to my research. You can pretty much tell the type of a value at analysis-time in PHP. Its expensive analysis though. It would be useful to be able to make some assumptions and back them out at run-time though, like assuming that the sum of two integers is an integer. > It is odd that the article claims that JITs for dynamic languages are never successful; there is V8 and TraceMonkey, and Parrot optimizes Perl 6 pretty well. Java is fast because of its JIT. The author claims that LLVM's JIT compilation doesn't work, but that's untrue; I'm not sure where any of this is coming from. I never claimed these things. I've never seen performance statistics for the LLVM JIT. Link? I've also never seen stats where LLVM beats GCC in execution time of compiled code.