Sorry I saw this and had to say something. I've been a developer for over 22 years and just because a release is a Beta, doesn't mean it has to be slow. I love Apple products as much as the next man (god knows I've got enough of them).
Every Beta Apple produce seems to be slower than the current "released to the public" version and this seems to be a trend I've noticed over the years.
At work we develop functionality in conjunction with performance as the two in our minds go hand in hand. Apple however seem to work on the functionality first and once it's close to acceptable, then work on performance. This is just an observation by m, but may not actually be the case.
What I hate on these forums are other developers shouting the odds of "Its a Beta". Yes we all know it's a beta, lets just accept it and move on. The idea of these forums are to get opinions from others and to see if functionality etc they are seeing is common amongst other developers/testers/users or if there is anything they are doing wrong which can be corrected with the help of others so only real bugs can get reported when necessary.
[/Rant over, move along now]
This is a great response. Anybody's who's ever really been taught *real* software development, as opposed to somebody who downloaded Xcode and pirated a Cocoa e-book, should know that when you code something, maybe a function, object method, class method, whatever, you code it to be as good as it can be. That means you want it to functionally work. You want to it be 'fast' (actually, you want it to perform within predefined parameters for performance) and you want it to fail safe.
When developing and writing software you absolutely DO NOT 'make it work and tidy it up later.' I don't believe Apple, or indeed any other large software company, does this. There may be some debug code in there but for public builds this code
should be disabled by declaring a constant. The compiler won't even then put that line of code in the binary. Sure, there are always tweaks and optimisations that will come later - no part of any piece of software is ever 'perfect' but the individual differences will be negligible and will usually improve resource consumption, not the end user experience.
I absolutely don't understand why certain myths seem to prevail year upon year. "Clean installs are better than upgrades." "It's slow because it's a beta." These things
maybe once had an element of truth about them but should no longer be taken at face value. Software development methods and tools have changed and been improved massively over the years.
As the quoted post states, every major iOS revision is slower than the last and that's sometimes understandable given that it's doing more but with iOS7 I'm left wondering what it's doing that makes it so much slower than iOS6. Like the original poster, I don't believe it's
inherently slower, but the animations do seem to take longer than necessary and that's certainly something that can be tweaked.
For now, I guess I shall simply say I believe iOS7 (GM) will be slower than iOS6. I have two iPhone 5s I'm willing to put side by side to back this up on release day.
