3 ms·
>"Until recently(?) the primary JIT back-end for PyPy was, in fact, still the JVM." That's not true -- PyPy had an experimental JVM backend early-in, but the f
by jnbiche 13y ago
>"Until recently(?) the primary JIT back-end for PyPy was, in fact, still the JVM."
That's not true -- PyPy had an experimental JVM backend early-in, but the first and flagship backend has always been the RPython one.
- voidlogic 13y agoMaybe he is thinking of Jython?
- nly 13y agoYou're correct, I was muddling up the projects (I really don't use or have an interest in Python) I thought RPython was only translated to C and compiled ahead-of-time.
- jnbiche 13y agoYou're right about that. To make a more correct analogy, I should have said that the main target has always been C, which RPython "transpiles" into. So the original and primary target has always been portable C, but there have also been experimental JVM, CLR, and JavaScript targets.