Yeah, but as I said it's different for each use case. For example, running that configuration means increased power consumption at home (or rather my fiancee's apartment nowadays).

It also assumes that I have a constant connection to the internet (*cough* take the DC Metro system *cough*). And what I meant by school is not the school's system, but my own systems I use for doing school work so it's not something they could provide anyway.

Anyway, the Maemo platform is a bit unique since its main problem (outside of Nokia's failure to support it) is a small userbase from being locked into one manufacturer (and also one device). With that you'll have less interest from commercial developers and its often easier to port or use an optimize app as a non-commercial developer than to redo an application's UI for the device. Heck, I'm surprised we got Angry Birds before Android did. At this point the only commercial benefit for developing for Maemo would be developing in QT (for future compatibility to Symbian and Meego).

Anyway, back on topic (on Apps). True but themes, locales, daemons (well I would argue daemons are often just as useful as apps but that's IMO) are just a subset of apps. Out of the entire Android market, even if the UI isn't optimized for the Samsung Tab, there are going be useful applications that can be used until a suitable replacement comes along. Then as developers either update their app, or competitors come along, you then get optimized Android apps for a tablet form factor. And unlike the Maemo platform, Android has the environment for that to happen.

Though interestingly Google has pretty much said that 2.2 is not for tablets, and that any tablets coming out now (using 2.2) will not have marketplace access. The Tab sneaks on by since its not considered a tablet by Google (screen size wise). So they are aware of the whole optimization issue.