Post comment on The Verge to
"Android's power management API can lead to 'no-sleep energy bugs,' according to Purdue researchers"
Reply to: by TruthIsFree
“I’m saying that whenever possible the platform should be designed to minimize the potential for programmer error negatively impacting the user experience”
And I’m saying that sometimes a platform requires that advanced functions be able to operate independently of any power saving functions of the OS. In this way, the OS is more flexible and more versatile.
Regardless, it’s a tradeoff, that’s for sure. Hand-hold the developer while stopping awesome new apps via arbitrary restrictions, or allow for the potential of API abuse negatively affecting user experience?
I personally think Android is doing the right thing when it comes to this, as it more closely reflects traditional desktop development. If something is using your battery power or preventing your computer from going into low power mode, then remove the program. It’s the dev’s fault. Notify him and get him to change it.
Reply to: by TruthIsFree
“I’m saying that whenever possible the platform should be designed to minimize the potential for programmer error negatively impacting the user experience”
And I’m saying that sometimes a platform requires that advanced functions be able to operate independently of any power saving functions of the OS. In this way, the OS is more flexible and more versatile.
Regardless, it’s a tradeoff, that’s for sure. Hand-hold the developer while stopping awesome new apps via arbitrary restrictions, or allow for the potential of API abuse negatively affecting user experience?
I personally think Android is doing the right thing when it comes to this, as it more closely reflects traditional desktop development. If something is using your battery power or preventing your computer from going into low power mode, then remove the program. It’s the dev’s fault. Notify him and get him to change it.