It’d seem odd to irreversibly change an app so it could never again run on an Intel Mac, at least not without warning.If it's translated, there's probably no need to keep the old binary - I imagine it'll be deleted.
How would the app installed on the disk get installed on an Intel Mac?It’d seem odd to irreversibly change an app so it could never again run on an Intel Mac, at least not without warning.
That could be the OS going through and verifying the application in a security-related way. I had an astronomy program that took 40-60s to start up every time. The developer figured out that "something" was wrong and macOS kept reverifying the program every time I started it. After an update the problem went away. It's only supposed to do it once. With an OS change or update the apps can also have to do things like rebuild caches and such and that can take a while on the first run.Well I’ve already seen the same thing with the new Ulysses, Affinity Photo & Designer on an intel Mac Mini with Catalina. First start-up bounces for some time, then fine from there.
That’s not a Rosetta problem.
It is my understanding that in fact, they do this.Could not Apple translate the apps on the App Store and create universal binaries for the M1 chip?
That would save a lot of energy as opposed to translating on each client.
It would be interesting to see a comparison of native Geekbench and Rosetta Geekbench.
That tells me the work Mac has limited memory for all the things it is running.god this is so true.....sometimes longer. my work mac takes like 30-40 seconds. best macbook pro they make too.
I think no, and this is a а big problem for entire Steam too.What about games? If I run my blizzards Diablo 3 launcher will trigger rosseta translation as well?
it tells me office is poorly coded. open office has no problem openingThat tells me the work Mac has limited memory for all the things it is running
How would the app installed on the disk get installed on an Intel Mac?
I actually don't think there is any reason to expect the original app to be modified - that could cause problems for apps that do tricky things with their executable files. (Think about .Net simgle file applications.)
Rosetta 2 works differently than Rosetta 1. Rosetta 1 had a cache, but it wasn‘t statically created.This probably sounds like news for newbies, but Rosetta always did this. It also happened on DEC Alpha machines running Windows NT in the late 90s when they had to run x86 apps.
...they did, repeatedly at WWDC.Cook should have made a point of this !
Possible Black Eye for AAPL !
I agree an informative message would be nice, but why the negativity? Truly not that big a deal while there is larger fish to fry, like: when are we going to see a working emulated/translated x86 VM environment?This is so Apple.
Is it really that hard to show me a message like “Yo, give me 20 sec, I’m doing X”?
UX gone down the drain just to hide “the nitty gritty” from the user.
Where does it state that Rosetta 2 decompiles and recompiles? A one time machine code translation is not necessarily the same thing. You can arrive at an ARM binary in two ways: compilation of source code and translation from existing machine code. I've worked in compilers before and IMO the latter is a more difficult task and achievable without decompilation into an intermediate, higher level language. It is possible the task involves an intermediate byte code representation beneficial to migrating from x86 to ARM. That's not reverse engineering and arguably also not decompilation.If Rosetta 2 de-compiles and then re-compiles for Apple Silicon instead of translating on the fly, would this mean that many AMD64 applications can not legally be run on apple Silicon because their license agreements prohibit reverse engineering and many jurisdictions allow restrictive licenses that don’t transfer ownership of the software to the customers?
If Rosetta 2 de-compiles and then re-compiles for Apple Silicon instead of translating on the fly, would this mean that many AMD64 applications can not legally be run on apple Silicon because their license agreements prohibit reverse engineering and many jurisdictions allow restrictive licenses that don’t transfer ownership of the software to the customers?
There will probably be a lot of hair splitting around this by companies akin to patent-trolls, but the decompilation step is only very partial. It never leads to human readable sourcecode on your computer.If Rosetta 2 de-compiles and then re-compiles for Apple Silicon instead of translating on the fly, would this mean that many AMD64 applications can not legally be run on apple Silicon because their license agreements prohibit reverse engineering and many jurisdictions allow restrictive licenses that don’t transfer ownership of the software to the customers?