Is this already gone for iOS, or is it sticking around longer for iOS?
Is this already gone for iOS, or is it sticking around longer for iOS?
I sport an iPhone 6s. I guess it is unsupported from this year, but I have owned it since the December after it was launched. So it was supported for circa 6 years, give or take a few months. That was absolutely the longest any Apple iPhone was ever supported. Most get less (I want to say up to 4 years, but I have no actual figures to hand.) I'm not unhappy with the length it was supported to be honest. My previous phone was a Nexus 4 and that got way less, I don't think it was more then 3.
The length the Apple Watch series 3 was supported it perfectly acceptable, and I bet few bough outside of the last 2 years still have great battery life anyway.
Apple should have been more transparent about what they were doing, but it’s difficult to argue that they were operating in bad faith. I’d wager unexpected shutdowns would result in more aggregate “unwanted” upgrades versus degraded peak performance.
I won't cry bad faith, exactly, but it was bad that the phones would lose performance after a couple years without this being properly explained up front. Their battery replacement program also helped mitigate the issue, but now newer phones cost more to replace batteries on, also because of design decisions...
> #Batterygate
Pick one.
It was also used for a few misguided things over the years, like force-enabling Swift Concurrency backdeployment for apps submitted to the app store, which mostly just introduced bugs that only happened on app store/test flight installs for zero benefit.
My guess is that maybe they don't want to maintain multiple old toolchains to provide the on-demand bitcode->native build step on the app store servers?
Ah, I didn't know that. Thank you
By the way something similar happens on Linux where kernel syscalls have different numbers between archs, for example. (Although on mac/ios, syscalls aren't guaranteed to be stable even across minor macos versions; the only officially supported interface to the kernel is libc)
I wonder why: was there some benefit for Apple in doing this?
aka "no fun allowed"