I think this makes lots of sense and defer to the great comments above as to why.
As to how this could happen:
- In March 2019, the new (ARM) MacBook (not pro) is launched
- It’s surprising fast and uses an Apple GPU - and Face ID & two usb 3.0 ports & a lightening port.
- Memory and storage are soldered into the motherboard
- Like an iPad it comes in WiFi only or WiFi & 4G
- Its keyboard is more like the iPad Pro keyboard (and can be relatively easily removed & replaced by a service professional) as the body of the computer is built more like an iPad ie it ‘splits’ open.
- Like the latest iPhones, it’s waterproof
- It runs macOS. Xcode enables compilation to MacOS ARM.
- This version of macOS is forked from Intel macOS until the next major release version. Why?:
- Apple reveals that it’s been working with vendors such as Microsoft to get their apps onto ARM, using a pre-release version of the Marzipan APIs.
- Twitter also revea their iOS app has been ported to the Mac using this method.
- It also reveals details of the developer version of Marzipan which will more easily enable iOS devs to get their iOS apps onto the Mac - with more details coming to WWDC
- This ARM fork of macOS also has the revamped App Store.
- It’s revealed also a special point release of macOS featuring marzipan will be released about 6 weeks after WWDC (ARM only)
- In fall (October/November) 19, the next major point release of macOS is released featuring the App Store and marzipan apps
I'd agree with most of that.
The thing is that some people are missing though is that there is no need for apple to get software developers onboard yet. For some time applications uploaded to the app store have been in an intermediate byte-code format that apple can recompile themselves (without your source) to be native code for future platforms. This is one of the features of LLVM.
Additionally, most of the heavy work in a typical mac or IOS application (audio/video processing, etc.) is handled by the Apple frameworks. Which Apple can recompile as native (in the supplied/installed version of macOS) and your old application calling them will get native speed for much/most of the processing heavy things it is doing.
For the stuff that isn't being done by the frameworks - apple will rely on a new version of rosetta.
All this has been done before with the intel transition and it worked just fine.
The original intel machines had processors much stronger than the PPCs they replaced, but the software ran "about the same" via translation.
As the old machines were phased out and application vendors recompiled their code performance improved.
It will be even easier for apple this time around due to my notes regarding LLVM and the app store above.
App store apps will get recompiled by apple as native. Non-app store apps (if supported, I suspect so as there's a lot of them) will be no worse off than PPC native applications were running on intel in 2004 (or was it 2005? 2006? memory hazy).
[doublepost=1527594607][/doublepost]
I just have a very hard time believing that they would go full ARM. In case you didn't notice, Windows already tried x86 emulation on ARM and the performance is just rubbish. .
Microsoft are muppets when it comes to this. Don't think that just because Microsoft fail at something, it can't be done.
The windows software landscape is not the same as the apple software landscape. Apple's frameworks and the applications that use them are a lot easier for apple to port. Apple binaries for example have been capable of being multi-architecture since back in the NEXTSTEP days.
Microsoft? Nope...
Microsoft's win32 platform is a dogs breakfast, the applications that run on windows generally reinvent libraries or include rafts of third party code microsoft do not control to get things done. The frameworks apple provide are far cleaner and more likely to be used by a developer.