"IronPython, like JPython, is an attempt to ‘bastradise’ a programming language or framework."

"Microsoft wraps Free technologies with proprietary ones that impede interoperability and introduce patents."

(in regards to why he's anti-Jython) "Sun hired two prominent Python developers, IIRC, in order to attract developers to its stack. "
 

• IronPython and Jython are 'bastardised' programming language implementations because Microsoft/Sun hired prominent Python developers
• IronPython does not work without XAML

Umm...does this guy have any idea that Google hired Guido Von Rossum and that he spends 50% of his time working on CPython?  Also, I hear there's quite a few Googlers using their 20% time for CPython.  I'm not bashing Google here either - having people spend time on various Python implementations as part of their job is a good thing for Python!

As for IronPython 'not working without XAML', I'm curious if the author of the blog entry has ever even used IronPython (or CPython for that matter).  The minimum system requirements for both IronPython 1.x and 2.0 are .NET 2.0 SP1.  .NET 2.0 SP1 in turn doesn't even include Windows Presentation Foundation (aka XAML support) last time I checked.  Furthermore, IronPython hasn't changed the Python grammar at all and we run a large subset of CPython's tests and various other 3rd party Python packages to ensure we're compatible with CPython.  Last but not least, if IronPython was tied into XAML...it wouldn't run under Mono.