| | | >> Look for bendgate related tags.
I don't think the numbers are that great; there is a substantial "echo chamber" on most of these sites and I think that's what most of it is. There are evidently some people having problems, and they will be handled in due course.
While the iOS8 bugs are pretty normal, the 8.0.1 fiasco took it to a much more serious place. And I think Apple really needs think about why/how this happened.
Having used Objective C for a couple years now (and I've come to like working with it), I sometimes wonder if it isn't time for Apple to revisit its "best practices" standards for Objective C code. When a subsequent release creates as many problems as it solves it is time to look at coding standards and see why, in this day of object oriented programming, that is happening. One of the key aspects of OOP is prevent this very thing from happening by isolating structures and variables within their respective classes. Apple's current recommendation of using properties over member variables opens up the code this kind of problem (for this reason, I try hard to avoid the use of properties or at least I'm careful to make them readonly). Perhaps SWIFT will help with some of these as I've not really had a chance to work with it as yet.
But the changes in iOS 8 are not cosmetic, imo. They cut pretty deep in some areas and that could have something to do with it.
It is cool to be able to say, "Everyone was on ios7 in x days" -- but the downside of it is the bugs can affect a large number of users instead of a small minority. They have control over the rollout process; why not offer the updates to, e.g., 5% of devices instead of 100% in the first week then accelerate the rollout if and only if things go smoothly? It is one thing to have a few glitches and quite another to have devices become totally unusable as a result of patches built too quickly. |
|
