4 ms·

SO, you are actually saying the hardware you have is crap. I guess with the newer phones (nexus one, xperia x10) the UI will be as responsive as you know it fro

by buster 17y ago

SO, you are actually saying the hardware you have is crap. I guess with the newer phones (nexus one, xperia x10) the UI will be as responsive as you know it from your iphone and android will begin to shine.

ubernostrum 17y ago
It's worth pointing out that when the very first G1 showed up in customers' hands, people complained that there were issues with speed and responsiveness. The standard reply was "wait until the next phone comes out with better hardware, then Android will really shine!" It's been a year and three months since then. Each new phone on the market has bumped things up a bit, and now the top of the line has roughly doubled every hardware spec on the original G1. And there are still issues with speed and responsiveness, and the standard reply is still "wait until the next phone comes out with better hardware, then Android will really shine!"
dirtyaura 17y ago
Smoothness of UI is as much about software as it's about hardware. My Macbook Pro is a super-powered work horse compared to iPhone, but still many applications and web pages do not give a great smooth, experience. Reason? Because asynchronous, multithreaded programming, which is required for smoothness, ain't trivial with abstractions that current programming languages and platform libraries provide.
- deleted 17y ago
  [deleted]
- ggruschow 17y ago
  With any hardware made in the past couple decades, it's entirely about software. Plus, asynchronous, multithreaded programming isn't required for a perfectly smooth interfaces. Consider the enormous amount of instantly responsive software on 1 to 4mhz 6502s (Atari 2600, NES, C64, Apple II, Atari 8-bits, etc).. Every current platform, even the phones, can emulate those at multiple times real-time speed, so the hardware is certainly capable of it. In the 2600s case, it didn't even have video memory and a video chip to help the CPU. The programs had to be timed to output straight to the TV at the exact speed and time the TV needed data. No threads or asynchronous events to help there.

by buster 17y ago

ubernostrum 17y ago

It's worth pointing out that when the very first G1 showed up in customers' hands, people complained that there were issues with speed and responsiveness. The standard reply was "wait until the next phone comes out with better hardware, then Android will really shine!" It's been a year and three months since then. Each new phone on the market has bumped things up a bit, and now the top of the line has roughly doubled every hardware spec on the original G1. And there are still issues with speed and responsiveness, and the standard reply is still "wait until the next phone comes out with better hardware, then Android will really shine!"

dirtyaura 17y ago

Smoothness of UI is as much about software as it's about hardware. My Macbook Pro is a super-powered work horse compared to iPhone, but still many applications and web pages do not give a great smooth, experience. Reason? Because asynchronous, multithreaded programming, which is required for smoothness, ain't trivial with abstractions that current programming languages and platform libraries provide.

deleted 17y ago
[deleted]
ggruschow 17y ago
With any hardware made in the past couple decades, it's entirely about software. Plus, asynchronous, multithreaded programming isn't required for a perfectly smooth interfaces. Consider the enormous amount of instantly responsive software on 1 to 4mhz 6502s (Atari 2600, NES, C64, Apple II, Atari 8-bits, etc).. Every current platform, even the phones, can emulate those at multiple times real-time speed, so the hardware is certainly capable of it. In the 2600s case, it didn't even have video memory and a video chip to help the CPU. The programs had to be timed to output straight to the TV at the exact speed and time the TV needed data. No threads or asynchronous events to help there.