Originally Posted by solipsism
Are you moving the goal posts to say that Apple shouldn’t ever have an issue with a development build of iOS?
Not at all, what I'm saying is that somethings should be stabilized well before a Goldem Master. Things like the kernel, network stack and other basic components of your OS need to stabilize well before you print your final build.
I look at it as an upside down pyramid, with the kernel at the very bottom followed closely by the networking stack and other low level drivers. If these are not right you can't possibly expect the upper levels of code to work correctly nor be especially easy to debug.
So if the indications are correct, that is a change was made that impacted networking right before GM release then yeah it reflects poorly on Apple.
Just because it’s GM doesn’t mean it’s without issue;
No software is without issue, I'm certain we agree with that concept. In this case what bothers me is breaking something like networking one rev from release.
do you think these are sent to devs for the fun of it?
Not at all. On the other hand how many developers out there dig into the guts of their code and disturb stable logic right before a major release?
It’s also why there are point updates to major, feature releases. This is software, there will be issues that crop up.
This is my whole point, it is software which is composed of many components some of which are key. These key components need to be frozen well before the rest of the release and they need to be stable. Especially in the case of iPad where the thing is close to useless without WiFi. An iPad without WiFi is like a tractor without wheels, both can be useful but you need wheels to go anywhere.
Frankly I haven't been in contact with any developers in the last few weeks so maybe this WiFi rumor is all bunk. However back around the time of iOS 4.0 release more than a few people where surprised that Apple went with what they had due to all of the known bugs. I really have this fear that Apple is just becoming very sloppy with iOS releases. It is one thing to have to release point releases for things you didn't catch in QA, it is a whole different ball game when you release point releases to fix things that where previously released very broken. Broken it was if you where anything but a trivial user.
The other way to look at this, at keast personally for me, is that I bought my iPhone 3G and my MBP (early 2008) within a few months of each other. OS/X on my MBP has gotten progressively better while iOS has gotten progressively worst. Sadly it appears that most of iOS's problems involve poor coding or software QC. If you step back a bit the whole iOS development history looks like crap.
The common refrain I hear is that your 3G is old. Anybody with any sense knows that is not an issue because hardware has nothing to do with memory leaks and other coding issues in iOS. There is a limit to how much slack I'm willing to give Apple and obviously some will give Apple more, but they need to know they are not making customers happy out here. We are not all fanbois bent over ready and willing to take everything Apple throws at us, some actually expect software updates to work.