321–330 of 501 posts
Earlier quoted context omitted.
If Jobs was in charge this wouldn't have happened
Antenna-gate (the iPhone antenna not working well enough if you held the phone) happened while Jobs was in charge.
Lots of bugs and issues happened under Jobs, but this was the usual press BS.
The iPhone 4 went on to sell 50 millions of devices or so with that antenna and nobody in the real world had much of an issue with it.
Earlier quoted context omitted.
Is there any definitive evidence for this? Has anyone benchmarked devices before and after upgrades to prove it? Edit: I don't mean CPU benchmarking which has been discussed elsewhere in this thread. More like usability testing, sequences of actions not invoking new OS features where possible, and also a second set of tests using new OS features because that's what most people's experience would be.
It's difficult to achieve because one cannot downgrade a device to some older version. So when 3GS became insanely slow with updates, no one could at random get a device with an old OS version.
It takes literally zero planning to do a test now and then do another after the update.
I've found a few examples here:
https://www.youtube.com/user/kabriolett
These don't support the argument that devices are slower after updates.
Earlier quoted context omitted.
I'm with you. Updated my 6+ and everything is tragically slow. 4-5 seconds just to get the Settings or Messages apps to open. Typing anything is unbearable - every time, the first word capitalises and then botches everything from then on. Basic functions within apps or opening the camera take so long as to render them near-useless. I have switched off any animations and performance tweaks that I thought might help, b…
iPhone 6 Plus here. Can confirm exact same issues. I ended up backing up everything and reinstalling from fresh. It's only just bearable now. Still noticeable 2s+ delays to open iMessage & and to get into Settings. Using the device for me has become completely joyless. In fact I have incipient resentment just looking at this p.o.s. It was once a great device. It's now hamstrung with bloat. I have stopped using it muc…
People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. The actual issue is that some developer at Apple screwed up their animation configuration when implementing the calculator redesign, and nobody tested adding more than two numbers together quickly. Multiple failures, none involving system performance. What's happening is: the operato…
Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms. What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely. Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy probl…
Earlier quoted context omitted.
> People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. Lag doesn't necessarily have anything to do with performance. I really don't think people are talking about performance at all. No one would seriously think that a modern smartphone could be dwarfed by a 35 year old calculator in terms of raw performance.
Well everything nowadays is slowed down by the 20 abstraction layers, so I wouldn't be that surprised if someone managed to make one slower than a 35 year old calculator.
People are talking about "lag" and performance, as if this was a "the system can't handle it!" issue. This is a misleading description. The actual issue is that some developer at Apple screwed up their animation configuration when implementing the calculator redesign, and nobody tested adding more than two numbers together quickly. Multiple failures, none involving system performance. What's happening is: the operato…
Earlier quoted context omitted.
What is debunked? That the CPU has not changed during the upgrade? No shit sherlock. Synthetic benchmarks tell nothing of the end-user experience. Does Apple sprinkle wait()? No. Does the system become more and more complex and Apple taking less time to optimize because it runs “fine” on the [latest - 1] hardware? Yes.
Technically the 6s is now [latest - 2] hardware. X/8/8+ have the A11 Bionic; 7/7+ have the A10 Fusion; 6s has the A9.
Earlier quoted context omitted.
Interesting. Bored before bed so ran a quick test using my iphone7 and Ios 11.x, Google's stopwatch. The time from wake to photo was ~2seconds (using the lockscreen short cut). The time from wake to home screen photo app to photo was ~5 seconds. * I had to start the timer myself then go back to using the phone so I believe I could cut ~500ms. Since I have Live Photo enabled, the 2-second shots actually have a few fra…
I really miss Samsung's 'double-click home button to use camera' on the Galaxy S6 and S7. Probably the most convenient implementation of a camera shortcut I've seen.
Earlier quoted context omitted.
Your solutions are a little off the mark. Treating the animation as the problem is merely treating the symptoms. What needs to happen here is pressing the button needs to immediately register the press elsewhere in the code. The UI animations and the button tap should be decoupled entirely. Then the user can tap away as fast as their heart desires and only the animations are going to continue on. That’s an easy probl…
My professor likes to tell this story about keyboard buffers that I never quite understood. Basically, in this old time terminal setup he would start typing the password before the prompt showed up or something and when it did, it would just sail through. Sort of like how I can apt upgrade while apt update is still running but fancier and a couple of decades before...
Earlier quoted context omitted.
What is debunked? That the CPU has not changed during the upgrade? No shit sherlock. Synthetic benchmarks tell nothing of the end-user experience. Does Apple sprinkle wait()? No. Does the system become more and more complex and Apple taking less time to optimize because it runs “fine” on the [latest - 1] hardware? Yes.
Technically the 6s is now [latest - 2] hardware. X/8/8+ have the A11 Bionic; 7/7+ have the A10 Fusion; 6s has the A9.