News for hackers. Stuff that matters.
Re:Android doesn't use the GPU for its UI by st3fan on Sunday September 12, 2010 @11:19AM (#1683778)
It can also simply be a matter of available (human) resources. Remember how the iPhone was missing Copy & Paste? Probably not because they did not know how to do it. More likely simply a matter of shipping priorities and resources. I think the same is going on here.
Re:Android doesn't use the GPU for its UI by mattparcher on Sunday September 12, 2010 @01:05PM (#1684043)
While this is a good case for prioritization, I would argue that Google has made a mistake by allowing the fundamental interaction model of the phone to suffer from unnecessarily poor performance, either by taking less-than-full advantage of the GPU or (less likely?) not dealing with the problem of “heavy garbage collection” that is cited by the first project member to respond on the linked thread.

Copy and paste functionality is nice, but smooth-as-butter scrolling and near-instant responsiveness, a la iPhone, (or lack thereof) arguably define the experience.

Re:Android doesn't use the GPU for its UI by flyosity on Sunday September 12, 2010 @05:55PM (#1684652)
Scrolling on an Evo or a Droid X is choppy, especially on a large webpage (zooming in and out as well). It's incredibly noticeable when comparing the most high-end Android devices next to an iPhone 4. If this isn't a priority, I don't know what is.