I think a much better approach than just a switch is to have dual processors. An ARM and an Intel CPU over the next five years. That way, tasks that only run on Intel allow the Mac to use more power and turn on the Intel processor. In all other cases, it would use a much lower power state of a twelve-core A-Series ARM SoC. This, if implemented well, could allow Apple and developers a path to ensure customers get the best of both worlds. Apple can show its prowess and SoC capabilities without leaving out Intel/x86/Windows and etc.
This scenario has never been offered but it seems to me to allow the best of both worlds. Apple could run its own graphics which would probably destroy anything AMD has available. The SoC can do certain things much faster and better than Intel. But for those Intel-only apps that are power hungry not alienate them.
It’s truly the best of both worlds. It requires some advanced code and a rosette model to emulate all possible for running as much as possible on ARM CPUs. At the same time, when it just isn’t feasible like with Adobe Premiere Pro or other intensive apps, allow Intel to shine.
This strategy would allow a win-win for Apple, customers, developers and etc. as Customer will not be left out in the cold and developers will have time to implement a new instruction set.
anyone want to give their thoughts?
Like having an Intel M3 coprocessor?... Then you would need a dual architecture kernel that supports both x86 and ARM instruction set, which would be a bit of work.
If you are thinking, well, what about T2 and Intel Core i7 etc, this is because Apple runs a separate kernel and OS called BridgeOS on T2 which also powers the TouchBar. They are separate, and interoperate via APIs, to have Intel as a coprocessor, and have a coherent experience, and draw on the same monitor or monitors, that's gonna be some kernel-level work on Apple's part.