There's enough crying about tab reloading on these forums to fill an olympic size swimming pool
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
iOS 10.1 Reinstates 32-Bit App Alert, Warns Older Apps May Slow iPhone
- Thread starter MacRumors
- Start date
- Sort by reaction score
There's enough crying about tab reloading on these forums to fill an olympic size swimming pool
That includes the APPLE Airport utility who hasn't been updated since 2014? or that one is already 64 bits?
nvm it is 64 bits...still not updated since 2014...i assume that won't happen until new routers are released.
nvm it is 64 bits...still not updated since 2014...i assume that won't happen until new routers are released.
Last edited:
"This Old App" May Slow
Your iPhone Down.
However, this nagging message you have
to dismiss will definitely slow YOU down.
OK
Your iPhone Down.
However, this nagging message you have
to dismiss will definitely slow YOU down.
OK
Does anyone know if Apple means they will remove just the store facing app or all possible traces of it? For example, I've downloaded some apps over the years but can still download the latest version via the purchased tab. Will Apple remove that as well or just the main link to the app?
At first glance this Apple 32-Bit App alert seems a little heavy-handed à la 'App-shaming', but in the greater scheme of things it should clean up and de-clutter the App Store while incentivizing App developers to maintain a higher standard of user satisfaction.
It's not too much to ask developers to keep their Apps reasonably compatible with periodically improving hardware.
WOW - did not realize old 32-bit apps have that effect
You didn't realize it, because in a lot of cases it simply isn't true.
It can't be avoided that 32-bit apps require loading of 32-bit libraries on 64-bit devices. It can't be avoided that 32-bit apps require mode switching of the CPU on 64-bit devices. It can't be avoided that 32-bit apps cannot fully utilize registers on 64-bit devices. These limitations are inherent and, while they may not be terribly important on a desktop or laptop machine, they are going to be more important on power-constrained mobile devices.
WOW - did not realize old 32-bit apps have that effect
I suspect the speed difference is so small not to care. Do people really think a faster iPhone7 will run 32bit apps slower than the iphone 6s?
Absolutely! Apple has control over the iOS ecosystem and it actually surprises me they haven't enforced your resolution point.
Apps that are unoptimised for device display resolutions look so bad, it can actually make the hardware look bad for Apple.
Take the Facebook app, it looks atrocious on the 12.9inch iPad Pro and the device has been out for a year
I have no problem with the message popping up once per app.
I also have no problem with a small developer who can't afford to update the app to 64-bit, but keeps selling it—as long as it does run. I'd prefer 64-bit, but I know it's very hard to make a living at this stuff, and I'd rather have 32-bit than nothing.
And now I want to play Peggle Classic!
I also have no problem with a small developer who can't afford to update the app to 64-bit, but keeps selling it—as long as it does run. I'd prefer 64-bit, but I know it's very hard to make a living at this stuff, and I'd rather have 32-bit than nothing.
And now I want to play Peggle Classic!
This is probably the intended chain of events. Old but perfectly nicely working hardware will be made useless because the only place where you can get software for it is controlled by a company that wants to make more money from hardware sales. The brand loyalty among Apple users are so strong they cheer when the master whips them!
That's not entirely true - Apple is capable of making all of their framework 64 bit and most of 3rd party libraries made in Swift / Obj-C are already compatible. Sure, there are some older libraries which are not 64 bit, but it still means that those "legacy" libraries/frameworks would be loaded only on demand for time when some app needs to use them. If you mix 32 bit and 64 bit apps in OS, you need to load both 32 AND 64 bit libs in memory. Take a look at Activity Monitor in macOS and turn on "kind" column. In my case, only X11 and some deamons are not 64 bit, all other apps are.
I am not fully against Apple removing the old crap from the App Store, honestly. With so much garbage being thrown onto the App Store these days, it would be nice if they cleaned up some of this un-optimized junk.
I might be misreading your comment but I think we agree. My point was that loading 32-bit binaries on an otherwise fully 64-bit OS is inherently inefficient for the reason you state, the required loading of 32-bit versions of libraries that are already present in 64-bit form.
Over on macOS I'm down to adobeUpdateDaemon
for 32-bit processes and, like you, need Xquartz sometimes. It's less important on my quad I7 with 16gb RAM of course but still slightly bothers me. On mobile, it's pure waste.
Last edited:
There is at least one reason for such apps to be around - in some cases, a company has withdrawn an older pay-up-front version of a game and replaced with with a new version that's "free to play", complete with timers and all sorts of other slimy things to try to nudge you into giving them money on an ongoing basis. In those cases, I'd rather keep running the old, not-updated, app (that's been withdrawn from the store) instead of following their pleas to switch over to their replacement app that offers a mediocre experience.
Even Apple hasn't bothered to update all their apps to support the newer resolutions yet - granted Field Test isn't the most important, but it's still a rough edge.
Yeah, there's the possibility you won't be able to upgrade to iOS 11 without removing all 32-bit apps from your phone and Apple could "prepare" your iPhone by scanning it, presenting you with a list of those apps and giving you the option of removing all of them. That would probably be the most effective way of getting everyone onboard the 64-bit exclusive train, improving overall performance for many users. "Alerting" users is just the first step.
Last edited:
Yes, the reality of moving ahead and basically just progress is "planned obsolescence".
I'm pretty sure it would "drag down" performance of the phone overall due to having to cache extra copies of libraries. Cache misses probably grow exponentially when the 64 bit libraries keep getting swapped out (of cache, not RAM).