2.1 or 2.0.1 wtf is going on already JUST FIX THE IPHONE

[Riemann Zeta]

At this point, better for Apple to take some time and get it right rather than rushing out a buggy release.

This is true. It is certainly obvious that the current OS 2.0 was a beta build that was just automatically promoted to release because Apple ran out of time before their July deadline. Microsoft made a similar move with Vista (which is perfectly useable now, but was buggy as an antfarm at RTM in 2006) and it really came back to bite them in ass. I hope Apple is putting effort into actually debugging 2.1, rather than just throwing in more useless GPS features.

There are two reasons I claimed that we are unlikely to see a 2.0.1: (1) the fact that it has been so long since the 5A347 build without a release and (2) the version 2.1 beta is completely incompatible with 2.0 and all apps require compilation. I would think that if 2.0 has already been pronounced dead and obsolete internally, they would not spend any more time developing it. Why keep shooting a dead horse?

 

[2002cbr600f4i]

Well, from where I'm sitting (and I could be wrong) it seems like most of the people with the biggest issues are those running 2.0 on the older non-3G hardware.

That's not to say I haven't had issues with apps, or even the whole phone crashing on my 16GB 3G unit... I've had it since release day, still running the 5A345 firmware. I can count the number of full system crashes on 1 hand. The occational app crash I can deal with. Full system crashes are more annoying because it takes so long to boot, but they're nowhere near what I'd call "unacceptable".

Regardless, coming in here complaining about it isn't going to get the fixes/update out any sooner. It *IS* a bit annoying that many of these issues weren't found earlier in the development cycle, esp since we've been told that there were beta units out and about since January. However, as a developer, I can attest to putting out code that you think works perfect, passes all your internal tests, and then fails miserably when the consumers get their hands on them because they do things with them that you just don't expect, or because the "real world" use is much more complicated than anything you can reasonably simulate in the test lab (like changing 3G towers 10 times in 15 minutes, dropping from 3G to EDGE and back to 3G, etc.)

 

[gcmexico]

Taking 2-3 seconds to register that I've tapped a contact's name is what infuriates me. Laggy stuttering menus, arghhh.

*
absolutely true..but I can't see software update for at least another month, which sucks

 

[Vanarak19]

about 50% of the time, my phone lags.

is this a big deal? Yeah. This shouldve been worked out before release. Disappointed to say the least. They must of changed something from 1.1.4, because that was pretty smooth as far as operation goes.

2.0, while nice, is pretty much trash on my new 3g. It stutters like no other.

Apple, take your time fixing it. Because if you dont fix the issues the first release of 2.0.1, i wont buy another iphone again.

I still love my macs.

 

[TimothyB]

I've had a similar issue with graphic software, especially 3D apps that are very complicated and always bug filled. You'll be upset that there are major bugs, but you wait and wait and find out that instead of solving it, they wasted time adding new feature you don't care about, fix minor things, and you end with even more major bugs than before.

For the iPhone, I sure don't want Apple to rush these bug fixes, but I don't want them wasting time on new features when the bugs should have first priority and released right away.

After all that is worked out, then an update for new stuff, and take even more time making sure that update doesn't break anything again.

 

[Riemann Zeta]

Well, when you're wrong, you're wrong...and I was totally dead wrong about 2.0.1. I guess it has been waiting in the "wings" for a while now.

Glad to have it.