3 ms·
> Phones are much less powerful than PCs, but they feel comparably fast I beg to differ. My Droid Turbo is powered by a 2.7 Ghz quad-core CPU, yet often is in
by Sohcahtoa82 8y ago
> Phones are much less powerful than PCs, but they feel comparably fast
I beg to differ.
My Droid Turbo is powered by a 2.7 Ghz quad-core CPU, yet often is incredibly slow. If I want to open Waze and enter and address to navigate to, it's often 10-15 seconds from the time I tap the Waze icon on the launcher until the apps is loaded and the on-screen keyboard has presented itself for typing.
There are significant stutters when I'm trying to scroll while a web page is loading.
Fallout Shelter takes nearly an entire minute to load.
Sometimes, plugging in a USB charger causes the phone to basically become a brick for half a minute or more, as if there are tons of apps deferring processing until I'm on external power.
Overall, it often doesn't feel any more responsive than my original Droid back in 2010, which was only a 550 Mhz single core.
- AgentOrange1234 8y agoThere’s a lot to blame — the software bloat, delivery mechanisms, user-hostile decisions that prioritize ads, and all the rest. But clock rate is truly meaningless as a performance measure when the underlying architecures are different...
- Sohcahtoa82 8y ago> software bloat This came up on another thread here from a blog/article titled "software disenfranchisement". I mentioned that I think a lot of it is an unhealthy obsession with writing re-usable code that results in abstractions on top of abstractions piled onto more abstractions to the point where we get the infamous FizzBuzz Enterprise Edition [0] that I'm sure nearly everyone at HN has seen. We also have a problem of people statically linking massive libraries when they only need a small fraction of its code. > user-hostile decisions that prioritize ads Definitely a problem in mobile web browsing. Ridiculous that on a data-limited connection, ad networks still try to push video ads or ridiculous JavaScript code. > But clock rate is truly meaningless as a performance measure when the underlying architecures are different... Definitely true. ARM gets a lot less done per clock tick than x86. But I imagine a lot of the performance differences are done on purpose as a compromise to reduce power consumption, since ARM is so big on mobile platforms. This is entirely speculation on my part, though. [0] https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpriseEdition https://github.com/EnterpriseQualityCoding/FizzBuzzEnterpris...