dangonay | 06-20-2012 10:18 PM | Quote:
background multitasking will be opened up to all devs, thanks to libraries provided directly by Redmond. During today's presentation two different background tasks were demoed, VoIP and location
| You don't need "libraries" to write a multitasking App. Just skimmed over that Engadget article - seems a lot of people caught the mention of "libraries" and that this sounds a lot like how iOS does it.
Which isn't a bad thing.
Think about this. If there's one company who understands the hassles of not having multitasking (or relying on badly written Apps to "behave") it would be Microsoft. Remember Windows 3 with cooperative multitasking? It was the responsibility of the App to run for a portion of time, then "surrendering" to allow the next App to run and so on. Poorly written Apps would wreak havoc if they didn't "surrender" to allow the next App to run and hog all the processor time. People used to make fun of Windows and its version of multitasking (even the Amiga had preemptive). Windows 95 was a mixture of cooperative and preemptive while all current major OS's are fully preemptive.
Taking into account the history of MS and multitasking through its various OS versions I find it interesting they decided to go with a "services" based approach to multitasking instead of blowing things "wide open" and allowing any App free reign to run in the background.
Engadget should reword their article. Instead of saying iOS is the only one left without "true multitasking" they should have said "MS joins Apple in offering services based multitasking, leaving Android as the only vendor offering multitasking for any App". |