I understand it to be a tool that builds a bridge between the app and your computer.
If the app changes, the bridge needs to be rebuilt (in 20 seconds).
But, once the bridge is built, the traffic can flow fast. It’s still got a bridge to cross though, so it’s not totally native speeds. So, I suspect the “not quite as fast” does not include that initial conversion time, and that the speed differences you observe will vary wildly depending on the app.
I also don’t think a 20 second delay every week/fortnight/month per app will be that much of a drag for me, personally.
It’s akin to a byte code converter, the way Java works, for instance. On installation, it converts the x86 code to something more « digestible » by the M1 chip, but this code still performs less well than the native one. So it’s not full emulation, but it’s not running natively either.
Rosetta is a marvel — the exemplification of “it just works”. x86-compiled apps run just about as fast as they do on the most expensive Intel-based MacBook Pros, and faster, by a long shot, than on the last and best Intel-based MacBook Air. Let that sink in: apps compiled for Intel run faster in translation on the M1 than they do on actual Intel CPUs in MacBook Airs and most MacBook Pros. (…) You just don’t have to worry about Rosetta, period. The first time you launch an Intel app, MacOS will ask you if you want to install Rosetta. Agree, and installation flies by in a jiff — mere seconds — and after that, you’ll just never notice whether something is compiled for Intel or native Apple Silicon. (…) Rosetta performs great and compatibility is seemingly seamless. This is a technical tour de force, a home run for Apple that will mostly go unheralded by typical users because the entire point is that they shouldn’t notice or care.
I am looking forward to read more about the technical details.
And I know very well what a bytecode converter is. The implication is it’s not native. That would explain the difference in speed from native. And I know, from first-hand experience, that Apple owning the silicon means they can tweak the silicon to suit running this - if they want to. (Like we did on mainframe several times.)