Converting x86 apps to ARM statically is not a thing, and will *never* be a thing, because that would break mathematically proven theorems about computer science (beyond obvious cheats like just embedding the emulator into the "converted" app).
It's cache warming because the way the whole thing is *architected* is still a JIT. All it does is *try* (optimistically) to pre-translate stuff. It can't do it all. The app is still x86. The app still needs to see itself as x86. Function pointers must point to x86 code.
-
-
The app hasn't become an ARM app. It just has layers of translated code standing in for x86 code, but they still have to meticulously appear to the app itself as if they're not there. The app has to see an x86 world. And that's very different from true translation.
-
Using the word "translator" makes people think what Apple is doing is closer to recompiling an app for ARM at startup, and that is very much not how it works, at all.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.