+"From a software engineering perspective, 10 years is indistinguishable
+from infinity, so I don't care what happens 10 years from now -- as
+long as you don't blame me. :-)" - Guido van Rossum, Python creator.
+10 years is indeed a long time. PyPy was created approximately 10 years ago,
+with the exact date being lost in the annals of the version control system.
+We've come a long way during those 10 years, from a "minimal Python" that
+was supposed to serve mostly as an educational tool, through to a vehicle for
+academic research to a high performance VM for Python and beyond.
+Some facts from the PyPy timeline:
+* In 2007, at the end of the EU funding period, we promised the JIT was just around the corner.
+ It turned out we misjudged it pretty badly -- the first usable PyPy was released in 2010.
+* Another option for using RPython was to write CPython C extensions. Again, turned out RPython
+ is a bad language and instead we made a fast JIT, so you don't have to write C extensions.
+* We made N attempts to use LLVM. Seriously, N is 4 or 5. But we haven't fully given up yet :-)
+ They all run into issues one way or another.
+* We were huge fans of ctypes from the beginning. Up to the point where we tried to make
+ a restricted subset with static types, called rctypes for RPython. Turned out to be horrible.
+* We were very hopeful about JIT generator from the beginning. But the first one failed miserably,
+ generating too much assembler. The second failed too. The third first burned down and then failed.
+ However, we managed to release a working JIT in 2010, against all odds.
+* Martijn Faassen used to ask us "how fast is PyPy" so we decided to name an option enabling all
+ optimizations --faassen. --no-faassen was added automatically doing nothing. Then we
+ decided to grow up and renamed it to -O2 and -Ojit.
+fijal, arigo and the pypy team.