08/04/2011, 09:14 PM
first of all, I am not wrong. In fact, before starting this reply, I opened a new card and launched webOSroundup up, without waiting. I'll check on it when I'm finished typing this.
Originally Posted by Sanjay
Secondly, the resource is memory. Its a limited resources. Using memory to render objects the user isn't looking at is foolish, because it limits the amount of memory available to the user for the tasks he/she is ACTUALLY USING, Once all of the memory is used up, you'll either see a 'too many cards' error or the background application will have to refresh when you return to it. Both of those occurrences are far more undesirables than the solution HP has provided. While running applications in the background, the application in the foreground should get priority. That's just common sense. That doesn't mean stop the background app (which webOS doesn't) it means reallocate resources to the active app when plausible. Its plausible to remove resources away from rendering something the user can't see...
thirdly, I don't consider multi-tasking a waste of resources. But it is resource intensive. HP has found a way to use these resources efficiently while making sure the user experience is uninterrupted. HP's approach is the same one used by video game designers. If you wait until objects are in view before drawing them, you can use the resources you've saved improve what is actually on screen. I just don't get why you keep saying HP is moving away from multitasking...
Update: just as I suspected, WOR was fully loaded, by the time I made this post. The page rendered instantly when I switched. And by the time I returned back from WOR, my post was uploaded. I don't know what's wrong with your touchpad, but this thing multitasks nothing like
Apple's. I'm not even sure why you brought them up...on webOS, TASKS CONTINUE IN THE BACKGROUND...PERIOD.