4 ms·

I have a 6s and regret upgrading to 11. Slow and unstable. Frankly I don’t do enough sketchy crap on the phone to care about security updates as much as I’m sup

I have a 6s and regret upgrading to 11. Slow and unstable. Frankly I don’t do enough sketchy crap on the phone to care about security updates as much as I’m supposed to.

thunfischbrot 9y ago
Sketchy crap like checking your mail?
- Niten 9y ago
  Or like using Wi-Fi, given that iOS 10 will not be patched for the KRACK vulnerability.
0xffff2 9y ago
It always amazes me how subjective adjectives like "slow" and "unstable" are when referring to software. I too have a 6s (plus), and iOS 11 has been just as fast and stable as iOS 10 in my experience. This kind of disparity makes a lot of sense in the PC world, where everyone has slightly different hardware. I can't quite figure out why it's still common on a platform where there is relatively no hardware variation.
- JustSomeNobody 9y ago
  I keep screenshots of battery use in iOS. I went from 10.3.3 to iOS 11 when it was available. Gave it the obligatory 3 days to "stabilize" and was amazed at how crappy it was. Given my usage I was seeing about 4.5 hours Usage at the 50% mark on 10.3.3. On iOS 11 it was down to 3.25 hours. I tried all the Public betas up to 11.2B1. I DFU'd. I set up as new. I ran without my usual assortment of apps and just used the stock ones. I jumped through every single hoop I could and iOS 11 was just a downgrade for me.
- krisdol 9y ago
  I mean if I had devices side by side of different OSes, I’m confident I could measure it. Time to open applications, like the phone dialer and messages, is noticeably slower than ever before for me. Another issue is that now when I open my recent calls, it shows a cached image of its last state for a few seconds before it refreshes with the most recent state. Unfortunately, in those few seconds, I usually already clicked the contact I wanted to call back, only to see the screen refresh after my click and find out I’m calling someone I did not mean to call. This is the same annoying way that Safari treats the back button, but I’m sad to see that pattern creep into other apps. I’d rather see a loading screen than a false view.

I have a 6s and regret upgrading to 11. Slow and unstable. Frankly I don’t do enough sketchy crap on the phone to care about security updates as much as I’m supposed to.

thunfischbrot 9y ago

Sketchy crap like checking your mail?

Niten 9y ago
Or like using Wi-Fi, given that iOS 10 will not be patched for the KRACK vulnerability.

0xffff2 9y ago

It always amazes me how subjective adjectives like "slow" and "unstable" are when referring to software. I too have a 6s (plus), and iOS 11 has been just as fast and stable as iOS 10 in my experience. This kind of disparity makes a lot of sense in the PC world, where everyone has slightly different hardware. I can't quite figure out why it's still common on a platform where there is relatively no hardware variation.

JustSomeNobody 9y ago
I keep screenshots of battery use in iOS. I went from 10.3.3 to iOS 11 when it was available. Gave it the obligatory 3 days to "stabilize" and was amazed at how crappy it was. Given my usage I was seeing about 4.5 hours Usage at the 50% mark on 10.3.3. On iOS 11 it was down to 3.25 hours. I tried all the Public betas up to 11.2B1. I DFU'd. I set up as new. I ran without my usual assortment of apps and just used the stock ones. I jumped through every single hoop I could and iOS 11 was just a downgrade for me.
krisdol 9y ago
I mean if I had devices side by side of different OSes, I’m confident I could measure it. Time to open applications, like the phone dialer and messages, is noticeably slower than ever before for me. Another issue is that now when I open my recent calls, it shows a cached image of its last state for a few seconds before it refreshes with the most recent state. Unfortunately, in those few seconds, I usually already clicked the contact I wanted to call back, only to see the screen refresh after my click and find out I’m calling someone I did not mean to call. This is the same annoying way that Safari treats the back button, but I’m sad to see that pattern creep into other apps. I’d rather see a loading screen than a false view.