Linked by Stefan Michalowski, M. Sc. on Thu 19th Aug 2004 08:27 UTC
Editorial Lately posted on Slashdot, an article written by Joel Spolsky mentioned the trouble through which Microsoft went to make each version of Windows backwards compatible. In one case, for the game Simcity, they even changed the way memory handling was done when running that application. You can find additional stories of software tricks that recent versions of Windows have to perform in order to run these bug-dependant applications on the web. After reading the story, I discussed with a couple of friends how weird this was and how Free Software completely avoids this problem.
Permalink for comment
To read all comments associated with this story, please click here.
by reubot on Fri 20th Aug 2004 01:59 UTC

Even though I barrack for Linux, I belive that Backwards compatability is where work needs done (mainly in regards to libraries, as the kernel has backwards-compat worked out).

What I'm mainly ttrying to say is that dev's should relise that even though something is deprecated etc... they should still keep it somewhere in the API (maybe in a deprec. section), insteading of just going ahead and deleting it, meaning that essentially program will need work done to be compatable with the new version.