I understand just fine. I just violently disagree with you on every count.
Just because Apple chose to mix in some truly 'recent' -- not running apps -- in that list doesn't mean fundamentally it is not essentially a task list. It just makes it, arguably, a bad one. But if an application is running, it is in that list. Period. They mixed some other crap in. There is no harm in cancelling an app that isn't running, but this is where you go to cancel apps that are running.
It is an EXHAUSTIVE list of all running apps, the ONLY such list on the device even though you may have hundreds of apps installed that are capable of multitasking.
And that, Virgina, is why Apple chose not to include this so-called list of recent apps on iOS 4.x devices that don't support multitasking---because its primary use is for managing running apps. If its only use was for recent apps, Apple would have it put it on more devices, but they didn't. For 'recent app' functionality alone, it wasn't useful enough to put on non-multitasking iOS4.x devices, which got oodles of other iOS 4.x features. Multitasking was cut because of performance. I doubt showing the last several apps you ran falls into the bad performance category.
Think outside the box: Apple has hidden a task list by swizzling in some recent apps and calling it something else, but it doesn't change fundamentally what it is. Actually it is clever way of hiding conceptual complexity, but that fact it is only useful when you have multitasking tells you Apple is under no illusions about what this really is (showing just Recent apps would be 'useful' regardless of whether you had multitasking). So why are you?
Ignore away; it'd make my day!
Is this so hard to understand?!?
Jon: Yes, the list DOES show all apps that are running. 100% agreed. But it ALSO shows apps that are not running. Actually, after a while, 90% of the apps shown in the bar are not running. In particular, it also shows apps capable of multitasking that have been started and shut down again, either by the user or by the system.
So the bar does NOT tell you which apps are running. If my bar has 20 apps in it and I am under the impression that I need to free some resources, I may well "shut down" 19 apps from the bar and don't gain anything because none of the 19 apps were actually running.
KnightWRX: Thanks for supporting me in explaining how the bar actually works. And yes, by conception it's useless for showing what apps are running and for task management (although, of course, by chance you might even close a running app and gain some resources when pressing the X badge).
Both: Actually, I don't care how iOS works. My reasoning was that IF the indication whether an app is running or not has no useful meaning to the user, the blue dots (which ONLY tell you that an app is technically "running") is wasting the user's limited resources of attention. Of course, for the geek in all of us, the purely technical information might be "useful", but only for the sake of our technical interest. Look at all the other threads listed in Activity Monitor. Why aren't they being shown in the Dock with a blue dot? Because that's not conveying any useful information, for many possible reasons: either the thread is required by the system and must always be running, or it belongs so an app so always runs along another thread, or whatever. In any event, you all agree that it would be a waste of resources to show all those threads in the dock.
And now please understand that a dot indicating that an app is running conveys (will convey in Lion) no useful information to the user because it doesn't tell you that the app uses a noticeable amount of resources (this entirely depends on what the app does and how OS is managing resources. E.g. Photoshop
1. processing a batch of Photos takes 90% CPU and 80% memory, or
2. not processing any more = 1% CPU 80% mem,
3. with just a few open photos 1% CPU and 20% mem,
4. working on a photo but with others paged out 90% CPU and 40% mem,
5. not working with everything paged out 0.1% CPU and 2% mem
6. "suspended" with state written to disk 0% CPU and 0% mem
7. shut down 0% CPU and 0% mem.
So why on earth do you need the blue dot in cases 1-6 (or 1-5?) but not in 7 (or 6 and 7)?? This is totally beyond me. The blue dot doesn't even give an estimate of how long it would take to switch back to PS. 1 and 4 probably pretty long because of the heavy CPU load, 5-7 probably pretty long due to the amount of date to be read from disk, 2 and 3 probably pretty short because neither is the case. Again, the blue dot does not convey any relevant information.