Live data from Hacker News

iOS 11 reviewed

arstechnica.com

61–70 of 296 posts

Re: iOS 11 reviewed

#61
post #4

> 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…

> the problem is that you can't play phone games from 2009 on your 2013~2016 iPhone

Devil's advocate: you don't have to install iOS 11 on your four-year-old iPhone.

Re: iOS 11 reviewed

#62

Earlier 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?

Backwards compatibility.

Backwards compatibility doesn't come without trade offs in security, maintenance, resource usage, etc.

How far back should Apple go with backwards compatibility?

Do you also think that modern Macs should support 65C02 from the Apple II days? 68K Mac programs? PPC Mac programs?

Apple dropped 32 bit processor support in 2011. They will probably drop 32 app support in the next two years.

Re: iOS 11 reviewed

#63
post #58
post #43

Earlier quoted context omitted.

I find it hilarious that every time Apple does anything like this, people complain and Apple still sets record sales. You're fundamentally wrong and Apple knows it. They can rip the headphone jack out. They can deprecate 32 bit apps. They can remove TouchID. They can block installing third party apps. Keep complaining; neither they nor their customers care.

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.

I think Apple has a far greater advantage than MS did (if not quite the marketshare, although the markets are different). MS was never seen as 'cool' or an aspirational status symbol like Apple products are.

Re: iOS 11 reviewed

#64

Review 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.

I remember reading that iOS 11 also come with MAC address randoming so that you can't be tracked by wifi.

Pretty sure MAC randomisation has been in since iOS8.

Re: iOS 11 reviewed

#65
post #4

> 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…

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.

You seem to have no understanding whatsoever of the funding system and life cycle of games.

Games are generally funded by a publisher who retains all rights to the game, the developer is contracted for some time, then goes on to work on something else. A publisher is not going to pay for the update of a paid-upfront game from 5+ years ago, there's no ROI in that. Without a continuous revenue stream, publishers don't keep updating games.

Furthermore, both publisher and original developer can fold, leaving the game orphaned.

Re: iOS 11 reviewed

#67
post #4

> 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…

> the problem is that you can't play phone games from 2009 on your 2013~2016 iPhone Devil's advocate: you don't have to install iOS 11 on your four-year-old iPhone.

> 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.

Re: iOS 11 reviewed

#68
post #5

Also be aware that iOS 11 seems to be incompatible with Windows Server 2016. Seems to be an http2 implementation problem.

Seems to be Mail.app if it's a fault on Apple's side. I wonder if the Outlook.app works correctly?

Re: iOS 11 reviewed

#69
post #4

> 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…

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

#70

It's funny to see that they are not even able to implement an Ebook reader mode. Crowd sourced data to selectively enable/disable JavaScript for invasive/resource hungry websites will save a lot of battery too!

The Brave browser on iOS has per-site Javascript control.

How do you like Brave?
Post reply on HN