Linked by Hadrien Grasland on Fri 15th Apr 2011 10:24 UTC
OSNews, Generic OSes Ever since iPhoneOS (now iOS) has been released, there's an old fight going on about how multitasking should work on personal computers, and more specially what should happen to applications which are put in the background. Some advocate that they should be dipped in virtual liquid nitrogen and stop doing anything, like on iOS, which others advocate that they should continue to run in the background, like on desktop OSs. What about putting a little more flexibility in there?
Permalink for comment 470263
To read all comments associated with this story, please click here.
Member since:

I think it has something to do with network utilization and people who never shut apps down. In defense of the latter, some multitasking implementations, textbook example being iOS', really push this bad practice forward.

Many networked services require regular polling in order to check that the device/app is still connected. Which means that the network chip is regularly needed. If the power management daemon turns the network chip off after an amount of time x, and the polling interval is y, then if y < x what you get is a network chip that's permanently on... And that hurts battery a lot.

Also, there's the issue of poorly coded apps which are polling-based instead of being event-driven. There are some people who still code event loops this way...

Edited 2011-04-16 08:51 UTC

Reply Parent Score: 1