3 ms·
A mobile is a tool. It accomplishes a set of tasks for me. I don't want to be bothered with constantly worrying about my power supply in search of hypothetical
by sprout 16y ago
A mobile is a tool. It accomplishes a set of tasks for me. I don't want to be bothered with constantly worrying about my power supply in search of hypothetical benefits. I want a music player / messenger / Internet browser that I can plug into an outlet at my leisure.
Also, instant search with location / social data already works on my Motorola Droid. In fact, certain parts of it work worse on Froyo than they did on the previous release.
(Example: I used to be able to use voice search to say "Navigate to John Smith" and if I had a contact named John Smith with address information, it opened up navigation and took me there. Hopelessly broken on Froyo, and there's nowhere to submit a bug report because voice search and maps are both closed-source.)
But I guess mostly what I'm saying is that there are no hardware problems, it's all cloud data, cloud computing, and the main bottleneck is network, not CPU. Even so, the bottlenecks don't cause enough trouble that I'm willing to sacrifice battery to get rid of them.
- rakkhi 16y agothe main issue with that for me at least is offline useage. I often use my phone on the London tube with no internet access so having things offline or cached from the cloud is great. Local processing is absolutly required. LTE and new wireless standards may eventually change this but currently you can't beat something that runs locally. So more powerfull hardware on phones is absolutly required