But the real nut of it is that it has managed to make a chip so powerful that it can take the approximately 26% hit (see the following charts) in raw power to translate apps and still make them run just as fast if not faster than MacBooks with Intel processors. I’m sure we’ll get more detailed breakdowns of how Apple achieved what it has with this new emulation layer that makes x86 applications run fine on the M1 architecture.
There is both a lot to say and not a lot to say about Rosetta 2. But it’s clear that iOS, though present, is not where it needs to be on M1. Provided that the Catalyst ports can be bothered to build in Mac-centric behaviors and interactions, of course. But the app experience on the M1 is pretty firmly in this order right now: Native M1 app>Rosetta 2 app>Catalyst app> iOS app. It’s super cool for a second to have instant native support for iOS on the Mac, but at the end of the day this is a marketing win, not a user experience win.Īpple gets to say that the Mac now supports millions of iOS apps, but the fact is that the experience of using those apps on the M1 is sub-par. Yes, that’s right, no full-screen iOS or iPad apps at all.
SUPER POWER FX FOR MAC BOOK PRO HOW TO
There is no default tool-tip that explains how to replicate common iOS interactions like swipe-from-edge - instead a badly formatted cheat sheet is buried in a menu. The current iOS app experience on an M1 machine running Big Sur is almost comical it's so silly. That, however, is where the compliments end.
0 kommentar(er)
