Linked by Thom Holwerda on Fri 2nd Dec 2011 18:41 UTC
Permalink for comment 499008
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/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
Linked by Thom Holwerda on 05/16/13 13:17 UTC
Linked by Thom Holwerda on 05/16/13 12:06 UTC
Linked by Thom Holwerda on 05/15/13 23:03 UTC
More News »
Sponsored Links



Member since:
2006-03-18
What I've never understood about all this is how a developer takes the leap into a legacy free windows 8.
In the past, suppose you wanted to target some new feature in Windows 7. You could release one binary that does that and runs on all Windows 7 devices, but falls back or disables that feature, and would run on 99% of the existing windows desktops, whatever the windows version.
Now, to simply get a program that runs on all windows 8 devices, I've got to accept an entirely new programming model, and the fact that this program will not run in Windows 7 or below? So to delivery my product I have to deliver two entirely different binaries.
What Microsoft needs here is a Windows 8 "player" for legacy machines. This could be installed seperately, or embedded as an executable run time, and would allow developers to code to one API and deliver applications that run on all Windows devices.