"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."
To read all comments associated with this story, please click here.
Member since:2005-06-29
It gets you the most powerful and intuitive language and the ability to easily integrate it with a faster language that's not c/c++.
That's all I can think of. I'm not sure how much easier glueing in .net is as compared to using python's c stuff; but that's the only thing I can think of...
Well, there is one added benefit: If your code runs on both, you don't have to ask Windows users to download python. That seems small, but if you don't have to change your code it's a nice benefit!
Member since:2005-06-29
I think some people envision programming languages as going from being compiled into standalone applications, to being compiled into bitecode files that need to be interpreted. Tends seem to indicate that many of those same people also want one interpreter for almost every language there is.
Mind you that was entirely speculation, a momentary thought of mine which I wouldn't have even mentioned if it weren't for your question.
Member since:
Member since:
Seriously, who is going to use IronPython? What does it get you? The people interested in using Python are rarely going to be those interested in .Net so why combine them?