Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

iOS 11 reviewed

arstechnica.com

Post reply on HN
Print view View original

251–260 of 296 posts

Re: iOS 11 reviewed

#251

Post by valuearb »

masklinn wrote: post #69
scarface74 wrote: post #35

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?

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

Users paid most of that money to the apps developers, yet the developers won’t even recompile the apps to keep them on the store. Why should Apple punish all the other iOS users by sucking up memory to support abandoned apps they don’t use?

Re: iOS 11 reviewed

#253

Post by valuearb »

0x0 wrote: post #91
ohfouroneone wrote: post #15

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 think you have no experience with updating legacy iOS applications to modern SDKs. It is not just a matter of "recompile and push", it is: * Ensuring your code still works now that CGFloat and ints change size (can easily trip up code, I've seen things fail subtly and then grow into huge errors with combinations of NSInteger and "-1" etc) * Updating all UI to handle new behavior (yes, just linking with a new compil…

As someone who has been developing iOS apps for 8 years, it’s preetty easy. If you wrote code that depended upon sizes of fundamental types, you didn’t write good code. if you weren’t using resources to lay out UI, you didn’t think ahead. 2x and 3x graphics can be created from your originals with OSX preview.

It’s far easier to rewrite old apps today than ever. The tools are far better. The APIs are far better. Asynchronous code is trivial to implement with GCD nowadays.

The real truth is you won’t pay the developer for their time, so they won’t give it to you. It has nothing to do with Apple.

Re: iOS 11 reviewed

#254

Post by valuearb »

CJefferson wrote: post #88
ohfouroneone wrote: post #15

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…

Yea, your refusal to keep it up to date is Apples fault.

Re: iOS 11 reviewed

#255

Post by valuearb »

cocoviper wrote: post #111
ohfouroneone wrote: post #15

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.

Unfortunately a lot of developpers will not be able to update their app with the new Apple Guideline released this Year. They are currently blocking any app that look alike or have the same features. The guideline is so vague that a huge amount of Developpers including my company are forced to remove their apps or wait until apple removes them with no ability to update the app or communicate to the users that the app…

So you wrote clones of better selling apps?

Re: iOS 11 reviewed

#256

Post by valuearb »

oneeyedpigeon wrote: post #103
masklinn wrote: post #67

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

Yes, 5 years of constant updates for every phone is so short, especially compared to Androids zero years.

Re: iOS 11 reviewed

#257

Post by valuearb »

timbo1642 wrote: post #243
masklinn wrote: 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…

There are TONS of apps that aren't game that haven't been updated or are never going to be updated, but are good or very useful.

And they have been replaced by better, compatible apps.

Re: iOS 11 reviewed

#258

Post by valuearb »

cromwellian wrote: post #211

The 32-bit deprecation issue points to a larger issue of cultural decay. We can still obtain old Commodore 64s, Nintendos, Gameboys, and other old HW and run old SW on it. However, the way these walled garden DRM'ed online app stores work, once something is taken out of circulation, it's just GONE. You won't be able to buy an old iPhone 5 10 years from now and go download an old game. My son really liked this old Sim…

Why not? The App Store has always kept around your older apps when you stated on older operating systems.

Re: iOS 11 reviewed

#259

Post by toast0 »

tammer wrote: post #18
darthbanane wrote: post #8

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.

Eh it sounds to me that this is a great quick fix for the "I'm slightly too far from the AP to have bandwidth but I'm still maintaining a connection" problem I have almost daily. Will make an obscure security concern you've identified slightly more difficult to deal with. If you don't prefer trade offs like this, Apple likely isn't the best digital provider for you.

They could have built a nice ui for that, like cough windows phone. Turn wifi off now, but turn it back on in 1/4/8 hours/when I ask for it/when I get to a 'favorite place'. This was great when wifi at work mostly worked, but had bad days (turn it off until I probably left, maybe it'll work tomorrow). It's much less convenient on Android, because there's a good chance I'll forget to turn it on when I get home.

Re: iOS 11 reviewed

#260

Post by pier25 »

DigitalJack wrote: post #134
pier25 wrote: post #131

Earlier quoted context omitted.

I do it a couple of times every day. As for the quick access you can customize control center in the Settings app. It doesn't make much sense to me that you can't access that customization directly from control center, but Apple works in mysterious ways.

I think I misunderstood. I thought you were saying there was a way to add a link to the settings app to the control center. In other words, having a button in control center to open settings. I go there enough I wish there was a fast access to it.

I was wrong. I thought you could add any app to the control center but it’s only certain predefined features like flashlight.
Post reply on HN