5 ms·

Because (and that's a quote) "PyPy is unproven and experimental technology".

• pekk 13y ago
  I'm probably killing the joke, but what makes this absolutely great is that this is a reason for Perl 6 not to use PyPy
  • perlgeek 13y ago
    Developing an experimental language is a huge effort. And that effort becomes much larger if the underlying runtime environment causes problems. So either you need a proven, stable VM (JVM, .NET, mono, ...), or you need to have control over it, so that you can fix problems you encounter. Basing it on an experimental VM that you don't have control over, and that might have slightly conflicting goals (dynamic vs. gradually typed, for example, different calling conventions for routines) is precisely the problem we had with parrot, and we don't want to replace the parrot problems with pypy problems, we can avoid it :-)
    • lucian1900 13y ago
      RPython is a framework for writing VMs. You write an interpreter for your language in RPython (a statically typed language with syntax that is a subset of Python's) and the framework generates a VM with a JIT and GC and so on. You have full control over whatever happens in your interpreter, you can give the JIT hints and having types too early will not hinder the JIT. You also keep calling it experimental, but PyPy is a production-ready Python VM, which is more than one can say about Parrot or even Perl6.
      • duaneb 13y ago
        PyPy is production ready now, but that's actually a fairly recent development. I first heard about peel 6 in 2007, well before PyPy could have been predicted to work. Python barely had Psycho going for it. ParrotVM was the original form of PyPy, in some ways, and it just turned out to be too massively ambitious for a community that was already beginning to dwindle.
        • lucian1900 13y ago
          My point was that Perl6 and Parrot are still experimental.
    • pekk 13y ago
      Which PyPy problems did you have in mind?