|
|
|
|
|
by __d
3424 days ago
|
|
iOS applications are now compiled to an intermediate representation which is then translated to the target CPU instruction at install time. macOS applications could similarly be built to run on multiple instruction sets with basically no effort from the developers. Perhaps initially it might be restricted to first-party apps, or maybe AppStore apps, but having fat binaries is something macOS developers are used to doing ... The difficult bit would be the runtime migration from x86 to ARM and back. For processes that can restarted, it's easy. For running, stateful applications it would be more difficult. But I think things like Mail.app already use a backend daemon to manage their datastore: you could suspend the UI process and restart the backend daemon on the low-power CPU fairly simply ... |
|