5 ms·
AIUI the point of bitcode was that you submit one bitcode app, and Apple then compiles that down to per-model native apps. The last Apple Watch without 64-bit s
by pdpi 4y ago
AIUI the point of bitcode was that you submit one bitcode app, and Apple then compiles that down to per-model native apps. The last Apple Watch without 64-bit support was the gen 3, and that is no longer supported, so the use case for bitcode is gone. I expect they'll be happy to sunset that whole chunk of infra on their end.
- deleted 4y ago[deleted]
- danpalmer 4y agoThanks. I had remembered that Bitcode was architecture specific and couldn't remember if that applied down to the 32/64 transition.
- yoz-y 4y agoAfaik Craig said (probably in The Talkshow) that bitcode is not useful to do a 64bit transition as it is still specific to an architecture. It only allows for micro-optimisations.
- 0x0 4y agoEven the newer apple watches aren't fully 64bit, instead they run an architecture called "arm64_32" which uses 32bit pointers (which is probably why bitcode worked for this transition, I don't think 32bit bitcode could be used to produce a 64bit native binary)
- plorkyeran 4y agoXcode 14 introduces real arm64 for watchOS, and it runs on current watches. arm64_32 appears to have been just a transitionary thing (specifically so that existing apps could be recompiled to it via bitcode).
- blackoil 4y agoDoes that mean someone with gen 3 watch will not be able to download any new app?
- selykg 4y agoThat model is not getting the latest watchOS update this fall. So it’s effectively end of life going forward.
- iasay 4y agoThat's crap. They still sell it.
- theplumber 4y agoSo what? People buy more useless stuff all the time
- nindalf 4y agoApple takes great pride in supporting their iPhones for years after they stop selling them. This is the exact opposite.
- theplumber 4y agoThat's the PR. The reality is more nuanced #Batterygate
- mastercheif 4y ago#batterygate was an attempt to extend the life of iPhone 6 and iPhone 6s models with aged batteries by preventing unexpected shutdowns which were caused by the CPU pulling to much current when operating at high frequencies. 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.