But what about general purpose computing? I mean sure, it's going to beat Intel on performance/watt (anyone can do that lol) but what about peak performance? The only benchmark that stands out is "Build code in Xcode up to 2.8x faster." but how much of that is CPU vs SSD?
-
Show this thread
-
I'm still standing behind my prediction that Rosetta 2 is going to disappoint for number crunching, which is what people in any plug-in ecosystems are going to be stuck with for many years to come.
1 reply 1 retweet 19 likesShow this thread -
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.
3 replies 3 retweets 25 likesShow this thread -
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.
2 replies 1 retweet 24 likesShow this thread -
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.
1 reply 6 retweets 30 likesShow this thread -
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.
4 replies 1 retweet 34 likesShow this thread -
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.
2 replies 1 retweet 27 likesShow this thread -
Replying to @LuisH31441760 @_revng
I fail to see your point. I know decompilers exist. You cannot take decompiler output, recompile it, and get a working app out the other side (except in very simple cases), *especially* not cross-architecture.
2 replies 0 retweets 0 likes -
This is not decompiler but specifically a recompiler to recompile arm to x86_64 and then to fuzz the binary
1 reply 0 retweets 0 likes
That can never work fully statically for all apps. You can only do that in a subset of cases.
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.