Live data from Hacker News

iOS 11 reviewed

arstechnica.com

221–230 of 296 posts

Re: iOS 11 reviewed

#221

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

> I can't even put a copy online for people to download

Sure you can.

Put the source code up on Github and anyone can download and sideload it on their device. Don't even need a developer account to do that these days.

Re: iOS 11 reviewed

#222
post #149
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 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?

Re: iOS 11 reviewed

#223

Earlier quoted context omitted.

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…

No. Sometimes at work I don't want to use my employer's wifi. Sometimes I do.

But you don’t need to turn OFF WiFi for that, simply disconnecting (as the button does) will accomplish that too.

Re: iOS 11 reviewed

#224

Earlier quoted context omitted.

The arbitrary removal of 32-bit app support could be thought of as a heuristic to clear away abandonware. Which, for obvious reasons (security), Apple would like to have as little of in its App Store as possible. It also lets them aggressively deprecate and remove legacy APIs going forward.

Someone was/is tracking "zombie apps"; the percentage of iOS apps that aren't/can't be found is huge, like well over 70%. It's a longstanding practice at Apple. At some point hardware & software are old enough that not only are they not supported, they're pointedly ignored when some appropriate new development "breaks" them. Other platforms garner some favor by supporting ancient software, but I've long seen the subt…

I for one think that that's great. It helps encourage people to upgrade but it also makes things a lot easier to support. It's not friendly to the poor though. If you bought an older all aluminium macbook say in college and due to it being built like a tank you use it for 5+ years and it goes out of support what then if you're not making enough free cash to dole out on a 3k macbook?

Re: iOS 11 reviewed

#225

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.

Is there some sort of interface element that indicates when a setting can use force touch? Or does a user just have to do a long hold on everything to find out what does and doesn't accept force touch?

No, the discoverability problem still exists. You find out by trying it and hoping you remember the answer.

Re: iOS 11 reviewed

#227
post #89

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?

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

This is apple not microsoft. Move off of 32-bit, there's no reason to be on it. And corporations have the means (or there are third parties willing to help) to rewrite things to the new 64-bit mandate.

Re: iOS 11 reviewed

#228
post #74

Earlier quoted context omitted.

Can you explain what you mean? I type in both English and German. On latest iOS 10, regardless of which keyboard I have selected, I can start typing in either language and word prediction/autocomplete/spellcheck pretty quickly picks up which language I'm using.

Hmmm, maybe I don’t type in German enough but iOS has always given me trouble with German words trying to correct them to English words.

You may need to have the German dictionary installed.

Re: iOS 11 reviewed

#230

Gutted that they removed the 3D Touch App Switcher. That was was more comfortable and intuitive for me than double-clicking the home button. It's especially annoying that there was no good reason to remove it on devices that already had it. I don't know if they took it out because it didn't work on the new X or what, but dang. Feels like a significant UX hobbling to me.

They switched the way you do it on the X, so I guess for ‘consistency’ they removed it.

It wasn’t a bad feature but I could never remember it was there. Too many years of muscle memory double-clicking the home button.

Post reply on HN