So:<p>> It’s quite clear – Welcome to the future of Apple’s hybrid ARM/x86 platform<p>Meaning, in a nutshell, that we have two different system "loading" policies (the ARM policy and the x86 policy) having fun together on the same disk? Three if you count macOS and EFI as two different systems really.<p>So naturally this would make disk imaging complex. Seriously, why wasn't this documented (or better documented)?<p>I'm quite impressed with the author's polite tone. His list of unanswered questions is mind boggling.<p>[edit: perhaps not "mind boggling" ... maybe just alarming is a better term]
Another indication that Apple is no longer committed to professional customers of their computer line and their needs - iDevices get the required admin tools, but the target demographics for their computers are consumers and web dev shops where everyone tends to their systems.
The "Fun Bugs" section is really concerning. So, if you set the date on a new MacBook Pro to 1/1/1970, your MBP will fail to boot, because the OS in your keyboard still has a bug that was patched in iOS, but not in keyboardOS? I must be misreading that bit, surely?
From the article:<p>> Good news everyone: Mac imaging isn't dead... yet.<p>Also the article title doesn't mention breaking anything. So why does the title of the HN post say disk imaging has been broken?
The title of this HN post has been edited and does not reflect the article.<p>The correct title is:<p>"Apple’s new OS “activation” for Touch Bar MacBook Pros"
> We need a up-to-date portal with information regarding the future of mac management.<p>"mac management" is not in Apple's target market anymore. Actual professional usage ended with this mac laptop series.
Seems to me that if the OS can write the touchpad firmware, it's of dubious security value as a sort of "secure enclave" for fingerprint id or whatever else.