[IronPython] IronPython - thread to Python?
Keith J. Farmer
kfarmer at thuban.org
Thu Aug 26 21:28:16 CEST 2004
I agree that it's melodramatic, despite some points.
The thing that people seem to gloss over is that Microsoft has done *nothing* to purchase IronPython (assuming Jim would tell us if they had). That's prior art, owned by Jim, distributed under an OS license, and undoubtedly Jim declared it as his when he filled out the usual paperwork as a new hire. All Microsoft has done is hire Jim, who would give them the insight to make the CLR more friendly to development such as this.
They *could*, of course, make their own implementation, and submit it to ECMA. In that event, given their attitudes of late, I predict they'd be in consultation with Guido to formalize the language for submission, and then go on their own paths toward implementation. Same thing that's going on with C#, .NET Fx, and Mono: standardize the language, implement on your own, provide your own framework libraries as desired.
Frankly, I think taking Python and submitting it to ECMA would be one of the better things that could happen to it. At least then people can quit worrying over the platform and appreciate the language itself. I'd be happy myself to get back to Python if it were on the CLR, which is why I'm interested in IronPython.
From: users-ironpython.com-bounces at lists.ironpython.com on behalf of Nick Bastin
Sent: Thu 8/26/2004 11:54 AM
On Aug 26, 2004, at 12:10 PM, Robert Oschler wrote:
> I saw an entry on one of my favorite "news" blogs, Daily Python:
> On 2004-08-23 Ted Leung had this to say:
> "I think that the threat from IronPython is much worse than the Bill
> describes. Not only does IronPython have the potential to make
> scripting on the JVM DOA, it also has the power to destroy Python as
> we know it."
> This seems a bit melodramatic, doesn't it?
You should definitely read Ted's whole blog, and not just the blurb.
He makes some good points, and his blog is generally a good read. He
makes his living writing code in python, so I wouldn't just write off
More information about the Ironpython-users