Yes, I did. It's full of excuses for sub-par up front planning on the part of the Android team (much like the reliance on SD storage early on -- LOL at that bit of idiocy. I still see emails from people complaining that the on disk size of an app is a whole 3 megabytes. Mean while, in iOS land, Infinity Blade 2 is 800 Mb).

I also develop some of the biggest apps on both platforms and know more about their internals than I'd like.

I'm replying to this: "It has a much higher resolution than iPhone 3GS. In fact, it has six times more pixels." That has zero to do with the article.

There's nothing in my answer that's incorrect. Sure, your Galaxy Nexus can now sort of scroll reasonably smoothly (the one on my desk is okay, but still lags). But that's because of the GPU which is something like 6x faster than the GPU in a 3GS. And the fast dual core CPU helps, too.

That doesn't mean that Android hasn't come a long way in ICS. But it'll never catch up to iOS in terms of rendering performance/latency. It's an impossibility due to the underlying architecture.

>> "it has six times more pixels."

> That's irrelevant, since the GPU does all the heavy lifting.

The article: "There is still a limit to how much the GPU can do." (And the rest of that paragraph.)

Yes, having 6 times more pixes is very relevant. The GPU needs to be 6 times faster and have 6 times the bandwidth.

> I'm replying to this: "It has a much higher resolution than iPhone 3GS. In fact, it has six times more pixels." That has zero to do with the article.

Conclusion: You did not read the article - you just skimmed the first paragraph.