3 ms·
iOS 11 was the first Apple OS to not run 32-bit apps so I'm guessing the iPhone X that was released later that year (2017) with the A11 Bionic chip was the firs
by glhaynes 5y ago
iOS 11 was the first Apple OS to not run 32-bit apps so I'm guessing the iPhone X that was released later that year (2017) with the A11 Bionic chip was the first to drop 32-bit support.
- mumblemumble 5y agoYep, that was the one. Perhaps more relevant to the M1, though, is that OS X dropped support for 32-bit apps about 18 months back, with Catalina. The timing there seems just too coincidental to not have been done in order to pave the way for the M1.
- _ph_ 5y agoIndeed. I think throwing out 32 bit support in Catalina was in preparation for the M1 one year later. Not so much because the M1 is 64 bit only, as 32 bit x86 applications wouldn't have run on it either way. Perhaps to make Rosetta simpler, as it only had to support 64 bit code. But also with Catalina, all old and unmaintained applications did no longer run. Those applications, which run on Catalina, do run on M1. Which made the switch from x86 to ARM cpus much smoother for the users. The hard cut had been done with Catalina already - and this is the reason my private Mac still runs Mojave :p. When I get a new Mac, switching to ARM doesn't create any less backwards compatibility than switching to Catalina would...
- my123 5y agoRosetta supports translating 32-bit x86 instructions. However, there are no native 32-bit OS libs anymore. This means that you have to do the thunking back and forth yourself to call OS libraries. The only x86 program using this facility so far is Wine/CrossOver on Apple Silicon Macs, which as such runs 32-bit x86 apps...