Linked by Thom Holwerda on Wed 30th Nov 2005 16:31 UTC, submitted by Jeremy Jones
.NET (dotGNU too) "How can Microsoft kill Python? When I say 'kill', I mean 'seriously damage the relevance of Python'. I don't mean that Microsoft, as some have suggested, will work on IronPython for a while, get people using it, then hijack the language by seriously changing the syntax of it and thereby breaking compatibility with CPython. So, how does this damage the relevance of Python? If Microsoft, who is investing considerable time and money to create a .Net implementation of Python, only refers to IronPython as a 'dynamic language' and only pushes it as a 'scripting language', many people will begin to assume that that's all that it is good for."
Permalink for comment 67235
To read all comments associated with this story, please click here.
I love this article
by MightyPenguin on Wed 30th Nov 2005 18:26 UTC
MightyPenguin
Member since:
2005-11-18

"...refers to IronPython as a 'dynamic language' and only pushes it as a 'scripting language', many people will begin to assume that that's all that it is good for."

Maybe that's because that's what the language is good for? Last I checked it was a 'dynamic' and 'scripting' language. What needs to change here is not a redefinition of what IronPython is, but a wider acceptance of 'scripting' languages as more broadly useful then people widely believe.

Reply Score: 3