Who Do You Believe, Randall Stross or Your Own Lying Eyes?
daringfireball.net
daringfireball.net
I'm not saying that the nytimes article is right, but just that people who say it's wrong are wrong.
As an analogy, you can take the routers that were stupidly configured to use stratum 1 NTP servers. These misbehaving devices placed too much strain on the NTP "network" because they used it inappropriately. But it was only the NTP servers that a lot of these routers were configured for that were having problems. Yet no one would claim that it's the NTP network's fault for the issues.
A poor analogy:
- AT&T sells the iPhone.
- AT&T sells the service.
ergo,
- AT&T is responsible for providing quality service to the iPhone.
Anybody out there with a BB care to comment?
How does your LG perform in urban areas like SF, Seattle, or NYC? How's the 3G performance in those situations?
Many of the points rely on comparisons to other countries, but analytical people will recognize that problems can be caused by interactions in systems that otherwise work fine on their own too. For example, I had an old wireless router that worked fine with my Windows computers, but not with my Macbook Pro. But my Macbook Pro worked fine with other b/g access points. Without better information, how could we possibly tell which one is at fault? But Gruber (fanboy that he is) is drawing the conclusion that AT&T must be at fault.
As for the "Apple would have fixed it" assertion, or the question of why the number of complaints have gone up as iPhone users have, Gruber's blindness to his own biases is truly startling. You could as easily argue that AT&T has had three years to fix their network, so it must be Apple's fault because if the blame lay at AT&T's door it would have been fixed by now. And _of course_ the number of complaints will rise as iPhone users rise if the problem is some interaction between the iPhone specifically and AT&T's network: there are more iPhone users in existence to complain!
All in all this is very, very poorly done. I have no idea who's at fault but I do know that I won't be going to Gruber for anything more than entertainment if I'm reading about this whole fiasco.
I definitely think there's an issue with the iPhone's reception, but it's not so bad that I'd go back to my old "dumb phone".
It is completely possible that it is a problem with the iPhone, but one that is only visibly affecting the network when there's a high density of iPhones being used in a small geographical area.
It's like the whole controversial 'pre-fetch' setting on Fasterfox and other 'web accelerators'. It's fine for individual users, but it violates the contract of how network clients (browsers) are expected to act.
Once there's a sizable number of people using the technology it becomes a problem that affects everyone.
To say that the issues only occur in large metropolitan areas does not completely exclude the iPhone itself from being a contributing factor.
I never had any of these problems on T-Mobile, nor do those I know who currently have jailbroken phones on that network.
Operators need to boost capacity. Apple needs to improve their networking code.
Perhaps it's a little of both: AT&T's network is somewhat thin and overloaded exactly where media and tech-influentials most notice, and the iPhone is more fragile when facing that than other devices.