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
Now the other question is whether Apple can deliver a true high performance SoC to compete with the x86 solution on the high end. M1 obviously isn't it. 16GB max and no eGPU/dGPU support means it can only compete with ultraportable/embedded class x86.
Now if they can come up with something that competes in the same class as a PS5 SoC (to give a baseline x86 design by a competent company, because Intel have been failing for years), *then* things will get really interesting. But today is not that day.
![Adam [he/him]](https://pbs.twimg.com/profile_images/2328235588/mky7liyb93paqco9cfuk_normal.gif)
What we're seeing right now is Apple stretching the mobile/tablet market segment hardware, which they've gotten *very* good at, to encroach on Intel's ultraportable/embedded segment, which they've sucked at. Logical. Now can they go higher? We'll see.
Oh yeah, and One More Thing. Rosetta 2 *necessarily* uses more RAM than native execution. You need to keep the ARM JIT/AoT code/caches *and* the x86 code around, and probably some overhead on redundant JITting too etc. Now consider the 16GB limitation on top of that.
Very smart people have been doing high-perf emulation (yes it's emulation, *every* modern emulator uses dynamic translation and has for over a decade) for a long time. There is no such thing as "transpiling an x86 app into ARM". It's just not a solvable problem.
Rosetta 2 will be fast at some things, and suck at others. This is always the case with emulation. If you can hit the fast path on inner loops and get the SIMD right, then those things will be fast. If you get unlucky and hit some silly corner case, performance will tank.
Too bad Sony doesn't build VAIOs anymore. They could have built a nice high end laptop based on PS5 technology.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
