I like though, to see the JIT wave across interpreted languages (see Ruby). I'm also curious to see what's going to be the implementation.
Has that stopped HN before? We have devoted several top posts to the V language, LightTable, and several clearly doomed-to-fail efforts. This, in comparison is rather tame, from a legitimate source, and even if it just gives 2x performance, that will still be something.
PHP, for one, pulled it off, with PHP7.
I don't know the best route for python to get more performance but it probably involves allowing people to opt out of dynamism and basically doing what cython does but for all possible code.
Hasn't Strongtalk, Java, and JS put those concerns to sleep?
But just the most basic optimizations as done in PHP, a good lisp, scheme or lua would reach the 5x goal.
If there a precise difference between how Ignition and Turbofan interact that is not a tracing jit? I really thought both Java and JS implementations were tracing jits. Because if I'm going to whinge about technology I don't like I want to whinge about the precise problem. :)
It doesn't have to be this way though?
But, you don't get the JIT performance if you use the C extensions a lot, it's better for PyPy performance if you find a pure-python alternative for extensions used in "hot paths".
Yes!
But we aren't working with one of those.
where the code starts executing without JIT, while another thread is instantiated that is doing JITting in the background, and as soon as the JITting is done, JITted version takes over seamlessly for the rest of the execution.
Some people say 'dynamic JIT' (for example HotSpot) as opposed to a 'static JIT' (for example .NET.)