This is not entirely fair because the comparison point has changed. CPython is getting much faster, too, thanks to the optimizations stages before the JIT runs.
python is a language explicitly designed to resist any form of proper optimization. It just can’t be made fast
This is a common misconception! It is true that, of the Smalltalk descendants, Python was not designed for speed like Self or Java; but it was not designed to be slow or difficult to compile. The main technique required to implement a Python JIT is virtualizable objects, which allows the JIT to temporarily desynchronize the contents of registers from the contents of the heap; it’s not obvious and wasn’t in the first few iterations of PyPy. Additionally, it turns out that tracing the meta-level (see docs or the paper) is a key trick: instead of JIT’ing the Python program, the JIT operates on the interpreter, on the Python VM itself!
Please don’t show a close-up image of a snake, or at least add a spoiler! It’s irrelevant to the topic, and it just sets some of us on edge for no good reason. If it’s small, it’s fine, but this… holy shit, now I have a headache. It’s one of the reasons I stopped coding in Python altogether.
But looms at his little puppy dog face. :3
lol I get it, but it’s involuntary. I really wish I could like snakes but I don’t think it’s happening anytime soon.
