View Single Post
Capt'n Corrupt's Avatar
Posts: 3,524 | Thanked: 2,958 times | Joined on Oct 2007 @ Delta Quadrant
#9
Originally Posted by taixzo View Post
I think part of the reason is that Android is designed as a single-task OS. Sure, there's multitasking now, but it wasn't built in from the start, so each app behaves as though it were the only one, rather than recognizing that there are others. This means that if you are trying to do something with multitasking you have to more completely switch contexts, which is harder to do - whereas on Maemo you have applications based on desktop libraries that are designed to cooperate with each other.
This is not actually true. Android has supported activity based multi-tasking since API level 1, or the version before the first commercially released version of the OS. Some apps run completely as services (eg. VX Connectbox SSH) and only shut down on an explicit exit, which is analogous to the way it's handled on the linux desktop (for example).
http://developer.android.com/referen.../Activity.html

It is certainly more complex than process exclusive multi-tasking, but it also has the advantage of allowing the OS to determine how best to manage limited resources, and gives the app control based on a number of states. This is a big deal on mobile devices with limited memory and battery capacity. I also suspect would be very valuable addition on the desktop as well. It even simplifies user-management, as it is generally not required to actually exit out of apps. (I say 'generally' because some stubborn apps stay in memory and do not allow the OS to clean them up.)

And I agree that some apps do not cache well, or otherwise re-start when selected from the task manager. Of course, this is avoidable through better code, and the developer should be contacted.
 

The Following 6 Users Say Thank You to Capt'n Corrupt For This Useful Post: