SIGH.....
You're right, all the components are not the same, they are all SUPERIOR on the Nexus One and it STILL cant scroll smoothly. This is where you logic fails. pwned.
Are you seriously telling me that the radio has somthing to do with performance?? LOLZ!
About your OS comment...have you even read this thread?? We are stating that Googles OS is poorly coded hence the scroll lag even with the fastest hardware available all while a 3 year old iphone with crappy hardware by todays standards scrolls very smoothy.
As for your comment "In the future, better hardware may mask poor hardware efficiency but only until the visuals and other elements of the next OS version set the bar higher, making deficiencies transparent again", another failed logic and this is quite funny how bad your logic fails here.....scrolling is the most BASIC feature of an OS and has been around since the first release of both Android and iphone OS yet even with the latest hardware and YEARS of OS development Google STILL cant make it scroll smooth which is quite amazing how poorly its OS is coded.
All of your comments are been proven wrong.
You completely missed the point. It's not about the components being better or worse, the point is that "clock for clock" comparisons are only accurate when comparing identical platforms. As for the GPU, we have yet to find out how the N1's compares vs. the 3GS's GPU. The iphone graphics have set the bar high, I do know that. I saw 3d demos for the N900 and the N1, N900 was much better but there was room for improvement on the N1, how much is still unclear.
The radio operates all the time, it's extremely important how much of a CPU power it uses. I do not know how many radios are used in the majority of phones out there nor do I know how "CPU friendly" each of them is.
The scrolling through menus is always better with hardware acceleration. It can be optimized, the next generation of phones might address the issue and hardware acceleration may be enabled. None of the 3 may apply or all of them may, it's too early to tell.
Regarding the OS, the poor coding seems unlikely to be the culprit since it's been almost 2 years, enough time to address the issue. It could be the lack of hardware acceleration that's the reason. TBH, that's what I believe the reason is. I don't know why it's not implemented. To make things worse, up until the Droid, all Android hardware was vastly inferior to iphone.
Until the Android engineers team joins this discussion, we won't have all the answers. But I can tell you now, they would laugh at you clock for clock comparisons. Which is the initial point you failed to concede.
I'm positive that Snapdragon will be analyzed heavily with it's increase in market share. I can't peg it quite yet, it's better than everything else Android was running in the past. But 1GHz is a marketing buzz. The analogy is flawed but I would have no use for a car that does 200 mph if it takes 10 seconds to get from 0-60.