Agreed. Keeping in mind that what we know of WebOS suggests it's just a presentation layer on top of webkit and making the assumption that palm's "core apps" th

Agreed. Keeping in mind that what we know of WebOS suggests it's just a presentation layer on top of webkit and making the assumption that palm's "core apps" that provide services to lesser apps are of the same scope and resource usage as iPhone's background tasks, it seems we ought to be able to get a performance ballpark just by opening multiple pages in Mobile Safari. For those who haven't tried it, this doesn't work so well after 5 pages or so. And that's with static pages. Imagine if those pages were IM apps constantly polling the server for updates or youtube apps trying to stream movies? Certainly, I would assume palm's spent a lot of time optimizing this path that's (comparatively) unimportant to Apple. But I can't figure how that would buy anything more than incremental improvements. I've yet to see anything magic or revolutionary in their approach that leads me to believe they've cracked this basic limitation.