Ok, I just checked that benchmark, and I guess I must be blind... Please confirm...

The columns are ordered "this, other, diff" with (this=ipy11.pybench, other=py25.pybench).

The average run times are "13191ms, 7741ms, +70.4%" which means "this" (IronPython) took 70% _more_ time to complete the tests than CPython. Where is IronPython "way faster" then?

But I'll concede something: benchmarks that take 12 seconds to run don't represent any real world application.

For real world code, however, there's something missing: these tests disable garbage collection, and I'm assuming that goes both for CPython and IronPython. Ok, but on real world code, memory has to be relased eventually, and CPython does it continuously (reference-counting) while IronPython/.NET does it occasionally (garbage-collection). This means that, with garbage collection active, IronPython could problably beat CPython in short-run tests just because it is doing less work in that interval.

From my tests, PyDev seems to be nice, but I won't argue on that front, because I'm a <text editor>/<CLI>/<other tools> person and only use IDEs when I _really_ have to.