Since it hasn't been mentioned, an awesome part of iOS is the fact that Mobile Safari supports WebAssembly and WebRTC standards now. \o/
This! It still makes me sad that safari is updated as part of the OS like IE instead of out of band like Chrome.
iOS 11 reviewed
291–296 of 296 posts
Re: iOS 11 reviewed
#292Earlier quoted context omitted.
Do you realize that "legacy apps" are much more important to people who use them than the hardware that it runs on? Apple is a hardware company, and its need reason to push it. But what I do with hardware is run applications , and the applications matter more to me than the shiny (or not) box they run on, insofar as the box has the hardware to provide the UX that makes the software usable. I am not talking in abstrac…
Looks like everyday looper added 64 bit support in an update last week, fyi.
Good news for me, thank you!
Re: iOS 11 reviewed
#293Earlier quoted context omitted.
No the winner is the user who doesn't have to host hundreds of megabytes of 32 bit libraries in memory on their device.
That could easily be solved by offering 32bit support as an optional download, just like how 32bit windows10 prompts to install the 16bit ntvdm support libraries on first use. Or just like how iOS itself mounts a developer disk image provided on-demand by xcode during the first debug session, adding more items to the general ios settings menu in the process A few hundred megabytes is certainly a small price to pay fo…
It's a huge price to pay for a user who doesn't understand that their decrepit app is the reason the rest of their phone doesn't work as well as it used to.
The simple solution is for developers to recompile the apps. The developers of any apps that are truly still needed by customers, can easily convince those customers to pay for the update.
Re: iOS 11 reviewed
#294Earlier quoted context omitted.
That could easily be solved by offering 32bit support as an optional download, just like how 32bit windows10 prompts to install the 16bit ntvdm support libraries on first use. Or just like how iOS itself mounts a developer disk image provided on-demand by xcode during the first debug session, adding more items to the general ios settings menu in the process A few hundred megabytes is certainly a small price to pay fo…
It's a huge price to pay for a user who doesn't understand that their decrepit app is the reason the rest of their phone doesn't work as well as it used to. The simple solution is for developers to recompile the apps. The developers of any apps that are truly still needed by customers, can easily convince those customers to pay for the update.
But the phone worked "as well as it used to" on iOS10 with support for 32bit apps. So why would it not work as well as that? I think what will happen is the user don't understand why their precious legacy app doesn't launch at all.
Also, they could just continue to pop up an alert saying "this app may slow down your phone" like they already did in iOS10.
Also, I doubt there is much of a performance hit anyways. For example, the current facebook app is 64bit and it is a slouch to start.
Re: iOS 11 reviewed
#295> Practically speaking, do I need to be able to play phone games from 2009 on my 2017 iPhone? Not really. 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). But that's not what's happening, the problem is that you can't play phone games from 2009 o…
Considering the fix is simply re-compiling, I don't think this is the end of the world. There aren't THAT many apps that are both still very good, and haven't been updated in YEARS. Yes there are some, but not that many.
Re: iOS 11 reviewed
#296Earlier quoted context omitted.
It's not just the games. I've paid some 45 USD for a dictionary which won't work on iOS 11 on the same phone where it worked three years. The developer however wasn't able to renew the license, so he can't make a new version even if he would like to do it.
Is t only 32 bit? Three years ago we’d already had 64 bit phones for a year. Or is it some kind of API incompatibility?
I've bought the dictionary in 2013 and used on my previous model of iPhone too. My point is that the same phone which run the program for 3 years will stop running it as soon I allow the "upgrade" of the same phone to iOS 11. So I'm motivated to keep running iOS 10 and sacrifice security. Which is bad.