> I don't want this to turn into a typical iPhone vs Android forum dicussion, so I'm not really going to say anything else.
I agree, but I can't let this stand as implied fact.
> But browsing on a high-end Android phone (like Galaxy Nexus, Galaxy S3, One X, Xperia S) will be significantly faster than iPhone 4S.
My comparison was to a Galaxy Nexus running Chrome. Is it fast? Yes. I personally don't find it as fast and responsive as a 4S though. Just throwing power at Android doesn't solve the responsiveness issues it still has in ICS.
jellybean solved those problems. latency was definitely one area where iOS was ahead. if you look at general features, you'll find iOS has been playing catchup for about a year.
Audio latency is better but still not very good, compared to iOS/CoreAudio. I suspect it will never catch up simply because of the underlying design, Google simply does not have the knowledge necessary to implement low-latency audio.
I agree with this and don't think Google has the desire/skill to do anything about it. This is the biggest issue for Android from day one because the portable device is now considered a musical instrument and Android can't compete. Things are going to get shaken up again once Windows 8 tablets start running Ableton Live/Cubase so at this point Google should just wait and see what happens.
I agree, but I can't let this stand as implied fact.
> But browsing on a high-end Android phone (like Galaxy Nexus, Galaxy S3, One X, Xperia S) will be significantly faster than iPhone 4S.
My comparison was to a Galaxy Nexus running Chrome. Is it fast? Yes. I personally don't find it as fast and responsive as a 4S though. Just throwing power at Android doesn't solve the responsiveness issues it still has in ICS.