Linked by Thom Holwerda on Mon 21st Apr 2008 19:00 UTC, submitted by Adam S
General Development Ars' Peter Bright wrote an article today entitled "From Win32 to Cocoa: a Windows user's conversion to Mac OS X", in which he explains why he believes "Windows is dying, Windows applications suck, and Microsoft is too blinkered to fix any of it". These are rather harsh words, but there is a definitive element of truth in it. The article is part one in a three-part series.
Thread beginning with comment 310805
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: There is a valid question here
by kaiwai on Mon 21st Apr 2008 23:11 UTC in reply to "There is a valid question here"
Member since:

This sort of says that backward compatibility is a good thing but taken too far you are going to be slowly ground to a halt on grounds of performance, reliability and security.

There is a real question about how far Microsoft can take this line; and how they break out of it. Probably the key question is whether Microsoft are anywhere near making such a decision?

Well, I think I've mentioned this; they need to have a 3 year; announce at the beginning of a Windows release all the components which have been deprecated, then from there, announce that the following release will have it removed; in three years time. So you have a cycle of removing old cruft every three years, fixing up broken calls (and not creating backwards compatibility) everything three years.

If all operating system companies did it, it would then force third parties not to use well know deprecated API calls which they know are going the way of the dodo. Quite frankly, I am sick and tired of hearing third party vendors live the high life, fail to maintain their software, then turn around crying bloody murder when their crutch is taken away from them. Its time they started properly maintaining their software instead of expecting perpetual backwards compatibility.

As for Microsoft, there is nothing stopping them from making the change now; they could tomorrow throw out all the old unsafe calls in the next release, notify all the developers now - and there wouldn't be a single change in the market share statistics. The simple fact of the matter is, third parties will whine but update their applications knowing that they have no choice; customers will eventually upgrade, be at a slightly slower pace, and the cost of development and maintenance would decrease of Microsoft as they would no longer need to haul around ancient crap in their code base.

Reply Parent Score: 3