Re:Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
by Tehnix on Wednesday October 25, 2017 @03:13AM
(#15548127)
>Tired of people bringing up that "article" and the sensationalist media headlines. All that articles shows is that the CPU, given 100% utilization, does the same result as it did on iOS 10
But that is LITERALLY what people were accusing Apple of doing, actually slowing their devices to make them buy newer models. There might have been less conspiracy-esque claims, but jesting they were "sprinkling wait() calls in the code to make me upgrade" is not in that category - so I disagree with your claim that people weren't meaning that.
Anyways, this discussion has derailed, so I'm just gonna leave it at that.
Re:Try quickly typing 1+ 2 + 3 into the iOS 11 Calculator
by LeoNatan25 on Wednesday October 25, 2017 @11:52AM
(#15551136)
No—even at face value, "sprinkling wait()" does not slow the CPU, it slows the software running on the CPU; if you then manage to obtain 100% for your thread, that does not disprove that Apple has not added `wait()` anywhere in their code. In their code—software.
The real rebuttal of "slow" claims should be to look at the added features and security and discuss whether such trade-offs are worth the reduction in performance. For example, to make the user's data much more secure, Apple puts a lot of mechanisms behind XPC, which is inherently slower than mere API calls. These slow the system. Are they worth it, for the security benefit? That's the productive discussion we should be having.