Apple Watch update also...Hadn't noticed that! Thanks.
And I don't know.
Apple Watch update also...Hadn't noticed that! Thanks.
And I don't know.
Looking at things from the perspective of your own industry always leads to a "people just don't understand how difficult this job is" mentality, but I get you - and agree to a point, in relation to minor problems. But when new software DOES break things that should have been tested, it's not acceptable.And I still don't understand what the alternative here is: we stop getting updates? Would just one update a year make some people happy?
They counter with "well they should have the software not broken upon release." Software is rarely, if ever, released "broken." Issues are discovered after the fact because your test base goes from a few hundred to a few thousand to a few million. Sometimes features are held back for later release because they aren't ready yet, which seems to me to be the opposite of releasing broken software.
I'm going to make the assumption that people who say things like that have not worked in the tech industry. As always, don't you think if it was as simple as "not releasing broken software that doesn't need constant patches," that would happen?
As a retired software engineer, I can tell you that no one can possibly anticipate every possible scenario that could break the code. Engineers try to determine test cases that could possibly occur and write what are called unit tests that check the performance and correctness of each block of code with with tests that insert data they predict could happen. That is typically one person doing that job for each section of code. Engineers do not have the resources of millions of people. They do not have test suites of Asphalt 9, Uber, and Instagram running to find bugs. It is not their job to find apps that could break it. Engineers test their code on the micro level, seeing that each function and data structure does what it’s supposed to do. Code is only as good as its unit tests, which must all pass before code can be released to QA.nice, quick fix out. now fire the inept engineers who manage to miss it in the first place.
This was indeed a somethingburger. Let's start out with the fact Apple's QC did not discover this issue before releasing this new hardware & software. Then, Apple only did something about it when the customers who spent hundreds of dollars had to complain loudly about this overheating problem.Nobody is saying the phone doesn’t heat up. What dismayed me were all the conspiracy theories floating around, and the generally overblown reaction to all of this, and the general willingness to believe in lies like a rumoured poor thermal design being the cause. Delight in the prospect of another “gate” spelling trouble for Apple. Phones melting. Fire Tim Cook.
It turned out to be a nothingburger. Yes, there a bug. Apple will fix it. People will continue to enjoy their iPhones, and life goes on.
And by this time next week, the internet will simply have flitted to the next manufactured controversy to bash Apple over.
People don’t want the truth. They just want to hate on Apple, and they will blindly accept any rumour that fits in with this worldview where Apple sucks.
This was indeed a somethingburger. Let's start out with the fact Apple's QC did not discover this issue before releasing this new hardware & software. Then, Apple only did something about it when the customers who spent hundreds of dollars had to complain loudly about this overheating problem.
Also, let's not call this fixed yet, shall we? Yes the one benchmark Geekbench appears unchanged, but let's give the experts & sleuths who grace us with all of the free testing on various dedicated sites examine this issue further to see if this was truly a fix or did Apple just reroute this problem by gimping another feature that has yet to be discovered.
Oddly enough I didn’t experience any overheating on my 15 Pro Max but my mom did on her iPhone 15 Pro. She installed 17.0.3 today and it seems to have fixed the issue.I updated my 14 Pro to this overnight using the automatic update option, and this morning when I took my iPhone off the Mag Safe charger it wasn't warm at all. All the time in the past, it has been. Will be interesting to see if this continues, and that this fix was something deeper.
Granular? This overheating issue was all over the friggen news. Even my local 1-2 news stories a day site had this issue featured. Developers? Maybe, but I have yet to find any factual information on how they contributed to this problem other than Apple says so, which is why my "silence is deafening", because I look at facts & data, not excuses.Okay, if this is going to get granular, then let's get granular. Is it Apple's responsibility to test 3rd party applications (unoptimized applications at that)? If they also contributed to this heating problem, then shouldn't you be placing the blame on the developers of those applications, especially since they had access to multiple beta releases iOS 17?
Your silence is deafening when it comes to that, but yeah, let's solely put the blame on Apple's QC for not discovering an issue that may not have been their issue to begin with.
BL.
it then moves to QA who spend months writing tests plans and dreaming up scenarios that could break the code.
Except it was hit or miss. I didn’t notice any overheating. My mom did. 17.0.3 seems to have fixed it without affecting performance.Granular? This overheating issue was all over the friggen news. Even my local 1-2 news stories a day site had this issue featured. Developers? Maybe, but I have yet to find any factual information on how they contributed to this problem other than Apple says so, which is why my "silence is deafening", because I look at facts & data, not excuses.
Unfortunately I don't see it occurring any time soon - Google has been fighting that war for a while with Android 14 being the latest attempt to clamp down on badly written resource hogging applications that ruin the experience for Android users but there will be fall out when a whole new group of people will complain that their favourite app isn't working properly. If Apple does something similar to Android you'll hear people complain that their oh so important application, some random app written by some guy working out of a toilet cubical in Siberia isn't working then this forum will be filled with the brim of those individuals complaining.How does this prevent apps like Instagram from over-using CPU resources though?
Then why did he allow macOS Cheetah to be released which needed four revisions, followed up by Puma being released free of charge as an apology? And even then, it took until Jaguar for macOS 10 to be truly usable.
What about the fiasco of MobileMe? It was so bad that he publicly apologized for it when introducing iCloud.
All that happened under Steve.
Granular? This overheating issue was all over the friggen news. Even my local 1-2 news stories a day site had this issue featured. Developers? Maybe, but I have yet to find any factual information on how they contributed to this problem other than Apple says so, which is why my "silence is deafening", because I look at facts & data, not excuses.
Not for me - 10.0.1. Apple Watch 8.Apple Watch update also...
Hmm, i just updated my iPhone 15 Pro Max to 17.0.3 and my phone turned into a white screen telling me that it’s “Attempting data recovery”. It took about 15 minutes to resolve. My iPad Pro updated just fine.
Developers? Maybe, but I have yet to find any factual information on how they contributed to this problem other than Apple says so, which is why my "silence is deafening", because I look at facts & data, not excuses.
Apple confirmed that there was a bug in late September, and said that it would be fixed with an update to iOS 17. Some third-party apps had also been overloading the A17 Pro chip, leading to problems with heat dissipation. Apps affecting performance included Instagram, Uber, and more, and in addition to releasing an update to address the iOS 17 issue, Apple has also been working with app developers to optimize apps causing problems.
You may want to do some education on Media Literacy to understand how any why news stories circulate.Granular? This overheating issue was all over the friggen news. Even my local 1-2 news stories a day site had this issue featured. Developers? Maybe, but I have yet to find any factual information on how they contributed to this problem other than Apple says so, which is why my "silence is deafening", because I look at facts & data, not excuses.
Like I already said, “says Apple”. Got any objective proof apps were part of this overheating issue? I could not find any. Thanks.Then I would be questioning what you are looking at, because it was more than publicly stated that unoptimized apps were causing a problem. The proof? The very first post in this thread:
Perhaps looking further into how facts and data are discovered are in order, because this was glaringly obvious from the first reports of the overheating.
BL.
Like I already said, “says Apple”. Got any objective proof apps were part of this overheating issue? I could not find any. Thanks.
I used to beta MMOs a lot, and pretty much 100% within an hour of going live someone either broke something or exploited something, and servers were down almost the rest of the dayIf people got fired every time a software release had bugs in it, nobody would be employed.
Seems people side stepping this obvious issue.There have been user reports of their phones heating up when making calls, using the built-in camera app, and just charging. All of which don't involve 3rd party apps.
But yeah let's put the blame on 3rd party devs, because Apple said so.