You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
Do you see how it could be a *mostly* ahead of time translator?
That's exactly what I said, it does cache warming. The point is, it isn't a new paradigm. Using a Shiny New Word like "translator" is marketing speak to make people think it's revolutionary. It isn't. It's just good.
I mean....pre-translating literally the entire __TEXT segment feels like more than cache warming to me.
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.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
