Ok, fair enough. Nailed me on that one. But in all seriousness, it would be nice to see the critical components of What Constitutes Enough.

I use the browser mainly for reading news (e.g. BBC, Slashdot...) and Maemo related sites, oh, plus GMail. It crashes, as soon as it gets overwhelmed by content (heck sometimes dies on Application Catalogue on Maemo) and causes reboot. It also doesn't allow me to work with my calendar on Google.

I consider these to be part of core functions that my device should provide (for the 1000th time, as an Internet Tablet).

I don't want a new Toyota, SD slot, new roads or whatever analogy you guys are coming up with; just a reliable and functional Internet experience.

I haven't encountered crashes on those sites, so hence my perplexed state. Gmail works perfectly. I have, however, encountered much bugginess on AppMan as I've reported here (no reboots, just failure to refresh). Strangely, it straightened out a while back. Someone told me AppMan is sensitive to bad repositories and one *might* interfere with overall functionality. No idea if that is correct or not.

Repositories that do not respond will cause AppMan to fail to update - this is a pain, as quite a few non-Nokia sites go down and you then have to identify which one from the log and disable it, and then re-enable it some time later when it is back online. It would be far better if AppMan could ignore repositories that are down without bugging the user and failing to update.

Bingo! Now THAT I call a bug. It's UI Design 101: NO HARD FAILS.