Linked by Thom Holwerda on Fri 10th Feb 2012 00:09 UTC, submitted by moondevil
Permalink for comment 506634
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/23/13 17:52 UTC
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
More News »
Sponsored Links



Member since:
2006-03-18
So I get that the issue with the old Windows API stack is that if you allow unrestricted installation of even ARM compiled "desktop" binaries, eventually something is going to be installed that doesn't work well with power management, runs processes in the background that don't place nice, or runs stuff in the foreground that eats your battery alive.
WinRT is carefully crafted to make it very very hard to do any of these things. Whereas the older windows APIs allow just about anything - this is why MS had to carefully port Office to WOA, to make sure that these desktop apps behaved properly on more limited devices.
That being said, couldn't MS provide an updated subset of the older windows APIs? This would be a cleaned up API that allows for easy porting, but forces app designers to make sure that their desktop apps are touch friendly, don't require admin privileges to install or run, have portable installations, and play nice with power management.