Quote:
Originally Posted by dangonay
If state saving isn't significant, then why did both Android and iOS spend a great deal of time and effort incorporating this into their smartphone OS? It's heavily integrated into the multitasking abilities of both. In fact, you can't even code for Android or iOS without taking into account the idea of state saving.
|
Resources are limited on a mobile, so battery life was the key driver; memory is there too. With large screens sucking up power, allocating cpu cycles to (full) background apps is a bit of a waste, considering battery life > desktop style multitasking for the vast majority of users. App suspension style multitasking is a design tradeoff.
Quote:
Originally Posted by dangonay
Yup, unfortuately.
I went to the University of Waterloo and have seen so many software/tech companies come and go over the years. It would be sad to see RIM go under as well.
|
The smartphone market is huge in size and diverse in geography, price points, etc, and continuing to grow. They still have branding power, so I believe they'll carve out their slice of the pie when they update to a current-gen platform. Everybody, except the big two, are in the same boat three years behind.