They will as well find it confusing, if the system stops responding when the system is "swapping" and trying to do the desktop style multitasking (Maemo/Meego) without killing anything. The amount of RAM memory counts both in Android and in Maemo/Meego.

The UI for multitasking in Android is easy to learn, but I agree the UI can be hidden and unfound for a normal user if (s)he never bothers to learn it. There is a good point of having a LIFO list of recent apps and not having them in mosaic style. For a normal user, it is simplified to show just the recent used apps in the list, whether they are resident and running in RAM, stopped or killed. IMHO for an experienced user the list could show with some way the stage of the app (running, stopped, killed), like with some colored dot beside the name of the app. (So, I somewhat agree.)
There is other ways of multitasking UI available if the default one is too simple or too hidden.

(This is a often repeated conversation, ~OT, but ...)
I personally think in mobile devices Android's way of doing multitasking is better than Maemo/Meego's way of doing it. It saves the normal user better against laziness of app developers and against knowing himself how many and how big (RSS memory) apps a user really can run simultaneously in his system.

In Android, if an app developer wants one's app to behave nicely also over the stopped-stage, one can program it. And if one wants to make sure it runs 24/7, one can program it (the service class). But lazy programmers who do not care to do things nicely for a mobile device, deserve their app's internal stage to reset during the Android-stopped stage or be just killed if they abuse the resources.

If an app developer bothers to make a well scalable UI to mobile device, he should also easily make it well behaving with Android multitasking.
If he just wants to port an app from a desktop world to a mobile world without doing any rewriting, I doubt it will be useful either in Android multitasking system or in the desktop style multitasking system (Maemo/Meego).

And one can enable swap-memory also in Android if one wants to have same kind of behaviour as in desktop systems. But for good reasons Android doesn't have swap memory system by default. It is left for the experienced users, those same who can also live with Maemo/Meego's swap memory easily and know the limitations and penalties.

Those of you who diss Android's multitasking, I suggest to just try one of the latests Android devices, for example Note 3, to see where Android is going. Jolla claims "the best multitasking experience" (for a non-experienced user) with their first device, but it remains to be seen.

I wonder how Jolla has implemented the Activity Lifecycle in the ACL part of Sailfish. Do they swap away also Android apps, or just kill them more easily if free RAM comes short. The UI and usage of the ACL in Sailfish is a really interesting thing to see (IMO), and I hope they have succeeded well in it.