Linked by Adam S on Wed 15th Oct 2008 12:02 UTC
Permalink for comment 333956
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
More News »
Sponsored Links



Member since:
2008-04-10
If they're keeping a 6.1 version number just for the sake of application compatibility, the developers need a swift kick in the ass. I can understand checking for a specific version of a library, but doing a hard version check for the OS? I may be missing something here, and enlighten me if I am, but it just seems so bloody stupid. If I were writing an application, I'd have it check the system for the libraries it needs, not some arbitrary number that could have been picked at random. If I were to somehow alter the version number in Windows XP to something ridiculously high, would that break everything that was running before I did it? If it would, there is a serious problem in the way people develop for Windows.
Again, correct me if I'm wrong, I'm just expressing an underinformed opinion.