Earlier quoted context omitted.
It feels like they’re trying to educate me as a user that switching wifi off to save battery is not super smart. It’s true, the difference is minuscule at best (20-30 minutes of battery life) but maybe I want to micromanage to get these 20 minutes. Or because I am concerned about privacy. My take is that if you want to “educate” users on how best to use a feature you must leave them the freedom to do it wrong (depend…
You can turn on airplane mode to turn off all radios, then turn on the radios you want on if you really want to micromanage.
iOS 11 reviewed
121–130 of 296 posts
Re: iOS 11 reviewed
#122Earlier quoted context omitted.
Your comment reminds me of a time when the same was said about Microsoft. It will be interesting to see when/if Apple falls the same way MS did.
>if Apple falls the same way MS did Are we thinking of the same MS?
Re: iOS 11 reviewed
#123Re: iOS 11 reviewed
#124Earlier quoted context omitted.
It's not that games from 2009 don't run, only games that haven't been updated since 2009 don't run. All a developer needs to do is recompile and push an update.
I made a game in 2009, it was quite popular, got a bunch of positive reviews, I gave it away for free. I had to keep giving Apple £100/year just to let people keep downloading the game for free. At some point I tried recompiling it for a newer iOS, and I get hundreds of message about depricated APIs that I had to change to get it accepted by Apple. Instead I let it drop. I can't even put a copy online for people to d…
Re: iOS 11 reviewed
#125Earlier quoted context omitted.
The problem is not that you can't play phone games from 2009 on your 2017 iPhone, tying 32b deprecation to a hardware revision would actually have been nice (regardless of the hardware still being able to run in 32b mode). The latest processor doesn't support 32 bit code. All 64 bit phones can support the latest OS. Why should Apple waste time, resources, and space on the device to support 32 bit code?
> The latest processor doesn't support 32 bit code. Don't they, though? I've seen a few people assert that, but no hard facts yet. > Why should Apple waste time, resources, and space on the device to support 32 bit code? Because users paid good money for 32b applications and phones which could run them at the time, and this is going to hold back users updating on iOS.
Re: iOS 11 reviewed
#126Earlier quoted context omitted.
The problem is not that you can't play phone games from 2009 on your 2017 iPhone, tying 32b deprecation to a hardware revision would actually have been nice (regardless of the hardware still being able to run in 32b mode). The latest processor doesn't support 32 bit code. All 64 bit phones can support the latest OS. Why should Apple waste time, resources, and space on the device to support 32 bit code?
They could offer 32bit app support as an optional download, just like how 32bit Windows 10 still offers the 16bit NTVDM and MS-DOS support as an optional install on demand. Really sucks to lose 32bit support for legacy apps that used to work, especially when it might be a companion app for hardware/equipment that cost much more than the iPhone X (like your car).
I have some 32 bit apps that already don't work with newer versions of iOS.
Re: iOS 11 reviewed
#127Review is not thorough. One huge change in the control center is that the wifi “toggle” doesn’t toggle wifi off anymore (wait what?). It just disconnects from the current network and doesn’t reconnect for a minute or so. If you don’t want to be tracked by wifi APs it seems you have to force touch settings into wifi and disable the adapter from there. Huge step backwards IMHO.
Re: iOS 11 reviewed
#128Earlier quoted context omitted.
It feels like they’re trying to educate me as a user that switching wifi off to save battery is not super smart. It’s true, the difference is minuscule at best (20-30 minutes of battery life) but maybe I want to micromanage to get these 20 minutes. Or because I am concerned about privacy. My take is that if you want to “educate” users on how best to use a feature you must leave them the freedom to do it wrong (depend…
Turning off Wifi is not something anyone - whether average or intermediate user - should be needing to do on a frequent basis. Airplane mode already takes care of the primary use case, namely disabling all radios. Someone intending to disable Wifi "temporarily" and then forgetting to re-enable it may wind up paying hundreds of dollars for cellular data. That goes against the "it just works" mentality, which is "Wifi…
When I go for a ramble or cycle in the countryside there's no point having Wifi enabled for four or five hours with no APs within several kilometres, so I disable it.
Likewise I disable Bluetooth and GPS when not needed. Being a 'good RF citizen'.
Re: iOS 11 reviewed
#129Earlier quoted context omitted.
> Devil's advocate: you don't have to install iOS 11 on your four-year-old iPhone. That is in fact my plan, but is nonetheless frustrating.
The typical lifetime of an iPhone is so short, I can imagine that Apple will one day save themselves a lot of pain and cost and just limit each iOS release to a single phone / ipad release.
It's actually one of the main things that keeps me in the iPhone ecosystem.
Re: iOS 11 reviewed
#130Earlier quoted context omitted.
You can turn on airplane mode to turn off all radios, then turn on the radios you want on if you really want to micromanage.
You cannot enable airplane mode and then proceed to enable the cellular radio without first disabling airplane mode. At least you can't on an SE.