Linked by Thom Holwerda on Fri 31st Aug 2007 19:17 UTC, submitted by ganges master
Thread beginning with comment 267559
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
You know, with all the money Microsoft has, I never understood why they never did what Python is doing: keep the backwards compatible stuff but also make an OS that's free of legacy and can be as good as they can make it. They probably worried it would be a competitor to Windows. Oh well, that's what you get if you value money above all else.






Member since:
2006-01-14
I was in complete agreement with you, until I read the reply to your post. I still agree with you. I think it is important that if you recognize vastly better ways to do something that you aren't so committed to compatibility that you add awkward for the sake of backward compatibility.
I think one of the things that keeps Microsoft from innovating is the legacy support they have to have. You can put me in the category of a Microsoft opponent. But, you know they have talent. If they didn't have to maintain compatibility, they could probably release something even I would like. Being open source affords the luxury of not being obligated. And, I don't think they (Guido) ever promised not to break compatibility. I don't think they are promising they will never break compatibility again, either.
Edited 2007-09-01 01:03