Everyone is so up tight around here. Sure it's a beta, but obviously people are annoyed to have their battery life cut in half when they were expecting it to increase by an hour. Everyone is well aware that it's the first beta and that bugs are to be expected. No need for everyone to keep repeating it.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Beta 2 expected...
- Thread starter marmiteturkey
- Start date
- Sort by reaction score
- Status
The only guarantee there is really that there isn't any guarantee.
Fine, so long as those who expected fantastic battery life "out of the gate" stop b!tching about it.
By the same token, everyone knows the battery life is bad. No need for everyone to keep repeating it. Works both ways.
Why not just let those who like to bitch about battery life bitch about it as I'm sure we all are anticipating the arrival of b2.
If you have a kid that keeps complaining the sun is hot, just let him do it and walk away. It's not like you HAVE to click on this thread and disallow ppl wanting better battery life.
Go on the dev forum if you only want professional discussions.
If you have a kid that keeps complaining the sun is hot, just let him do it and walk away. It's not like you HAVE to click on this thread and disallow ppl wanting better battery life.
Go on the dev forum if you only want professional discussions.
Take a look at this website: http://www.thinkybits.com/blog/iOS-versions/
The last years beta 2 has been released 15 days after beta 1, which means Tuesday.
The last years beta 2 has been released 15 days after beta 1, which means Tuesday.
I would bet that it has better battery life than beta 1, but still not on par with an actual public release version.
I am referring to low power mode, but it is interesting how you claim it doesn't count. The more complicated the feature, the easier it is for a "simple" change to wreak havoc with the larger functionality, especially in legacy projects. And the code related to throttling background refresh, to disabling it based on battery life should be very, very close to each other. I wouldn't be surprised if it wasn't the same if statement (if low power or not yet time, don't run refresh), making it vulnerable to typos that cause it to run too frequently. Also having the behavior too far removed from each other is bad, since it means you have these sort of implicit behaviors that you can modify without realizing it.
So I don't agree with your statement that it doesn't count.
Which is fair, although some have commented that Facebook was being reported as their battery drain, and my comment was a bit of a guess. The main point is that pre-checkin tests tend to be terrible at catching bugs like this. The environment is too controlled, and usually lacks coverage in more complicated, legacy projects that don't have good automation. I've been in too many large projects with last minute churn to really be surprised that a bug this bad made it into b1 without being noticed. Too many ways it can sneak in without being caught quickly enough.
If this was a recent project started from scratch within the last 5 years, I'd be more surprised. But for a project that dates back to before 2007, and is part of a larger codebase that dates back before 2000, not so much. These older codebases just don't have the sort of testing in place to reliably catch bugs. And larger companies are notorious for being slow to put it in place for older projects. Customer/business benefit trumps engineering efficiencies, even when that lack of efficiency eats into the rate at which you can produce features and improvements for your customers.
A single data point does not a pattern make.
Based on the data from that page, it could be as little as 12 days (iOS 4.0 beta 1) or as many as 18 (iOS 5.0 beta 1). And past releases may not guarantee future ones.
I hope Apple devs troll the forums sopping up our desperation for entertainment like Biscuit Jesus.
- Status