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."
Thread beginning with comment 67296
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Uhhg...
by emarkp on Wed 30th Nov 2005 20:00 UTC in reply to "RE[2]: Uhhg..."
Member since:

Python forces it. Open your mind, you troll.

You don't see the inherent contradiction in these two sentences?

I've never had a problem with different coding styles in large projects in C++. Basic guidelines have been just fine.

Implied syntax is a problem, and it's the primary reason I can't do any serious programming in Python. It's a neat language, but the "whitespace==syntax" is a dealbreaker.

Reply Parent Score: 2

RE[4]: Uhhg...
by on Wed 30th Nov 2005 20:43 in reply to "RE[3]: Uhhg..."
Member since:

Never heard of COBOL?

Reply Parent Score: 0