I'm with you except that we're going to have to figure out heat dissipation first.
I can count the number of seconds I can run POVRay3.7 benchmark on one hand before it thermally throttles from hitting 85C. Quad core snap800 in Nexus5
It might be as simple as having some kind of docking station that takes care of the heat dissipation when using the higher-power states. A few manufacturers have already experimented with big.LITTLE configurations so I wouldn't be overly surprised if phones in the future have a lot of their power locked away unless it's needed for desktop level applications.
Another possibility is that the SoCs get a lot more custom hardware that makes some compute intensive tasks a lot easier. I remember at one point when one of Apple's new iDevices could encode videos faster than one of their existing workstations because the SoC had dedicated h.264 hardware baked in whereas the workstation had to use the CPU, which although much more powerful, couldn't be as efficient as dedicated hardware.
The other possibility is that the cloud becomes even more prominent and phones are mostly just dumb terminals that serve as interfaces and all of the heavy lifting and computational work is done in a sever farm. We're already seeing a move towards this with office software now that Microsoft is putting most of their stuff online as well.
But on the flip side, you don't have to wait all year for new features, with Android you get those new features and updates throughout the year as soon as they're ready, directly to the apps themselves.
Apple does the same with a lot of their apps now, though they still save some major changes for the OS release, possibly because the changes may require some of the new OS features. For example, they updated the podcast app a while back to get rid of the skeuomorphism.
I'm talking about major changes to the OS itself like the notification system that aren't something that can typically be packaged as individual upgrades. Also, Google only moved to that model because the carriers and manufacturers were so terrible about getting updates out to consumers.
my original ipad can't even update to iOS7 so it's not that. It's just the suck. It crashes to the homescreen when too many things are open, even though we didn't really see this happen originally. May have been iOS 4 to 5 causing it.
That could be, but it could be from web-page bloat as well. A lot of sites keep adding more media, javascript, and other cruft that eat up more and more memory. Safari on iPad seems to barf for no apparent reason a lot of the time even if there is plenty of memory available as I've had it randomly crash to the homescreen even when I don't have any other apps open.
The original only has 256 MB of memory, so I wouldn't be surprised if some websites can take a healthy chunk out of that or that there are some weird errors in the older version of the javascript engines that cause problems. It would be nice if Apple didn't bundle browser updates with OS updates though.