Oh my god, people...
His point is: "it won't fix 3G connectivity most likely as iPod Touch has the 2.0.2 update as well."
I think we can all agree that we get his point: 3G will not be fixed since non-3G devices were updated as well.
The long, grueling point that seems to be dragging on and on (now contributing to that problem...) is that this is based on a flawed assumption.
Let's run a little thought experiment...
Suppose that Stevie called all of his engineers into one room and said, "We have two big problems that are more important than everything else - the 3G reception issue on the iPhone 3G and the Not-Suck-Bit was accidentally set to FALSE on all of the 3 platforms." Stevie then divides all those engineers into 2 groups and sends one group to work on the 3G issue and the other to work on the Not-Suck-Bit problem.
The 3G Reception Team toils day and night, working on a fix. Meanwhile, elsewhere in Cupertino, the Not-Suck-Bit Team reckons that this should be an easy fix since it only requires one line of code to fix it. They appoint Jerry The Not So Bright Engineer to execute the fix while they all head up to Tahoe for some much deserved R&R.
Jerry isn't a complete idiot so he figures out that he needs to add "Not-Suck-Bit = TRUE" to the code somewhere. Oddly, the problems persist and the testing guys and gals (who didn't get to go to Tahoe because people are mean to testing engineers) report that the fix doesn't work. Jerry tries to call the other engineers for advice but perversely because of the 3G reception issue no one has any bars at Tahoe and his calls go straight to voicemail.
A full week passes and the engineers all return from Tahoe an hour before the next big staff meeting with Stevie expecting Jerry to have fixed the problem. They are shocked to find that the problem still persists. Someone pushes Jerry away from his workstation, does a quick Find on all the instances of "Not-Suck-Bit" and discovers that Jerry forgot to remove all the instances of "Not-Suck-Bit = FALSE" that are peppered all throughout the code in routines like SyncQuickly(), SearchContactsEfficiently(), KeepSafariFromFreezing(), DisplayCalendarWithoutHosingExchange(), DontCrashAllMyThirdPartyApps(), DontLocateMeInAustinTexasWhenILiveInOregon(), etc.
A mad flurry of keyboard activity later, the offending code is removed and the new build is sent off to the test team. Everyone meets in the staff lounge for the update meeting and Stevie says, "Well, a week has passed, where are we?"
The 3G Reception Team says, "We've isolated the problem, sir, and spent hours recoding parts of the modem and baseband, blah, blah, meow, meow.... The problem is now fixed and ready to be released to our doting customers." The Not-Suck-Bit Team, all with non-characteristic impressive tans, report that they, too, have fixed the problem and are ready to release the fix to the world.
Stevie says, "That's great. Let's roll these up into one release, label it mysteriously as Bug-Fixes, and release it first thing tomorrow."
Now.... reading comprehension test time:
Based on that scenario, isn't it at least plausible that the 3G Reception issue might be fixed and bundled in with other fixes that affect all the platforms? Remember, the release notes DID say that it contained "Bug-Fixes," not "Bug-Fix."
Phew... Don't we all feel a little better after clearing that up?
