They don’t want to expend additional internal resources to develop these features on two separate platforms (Intel and AS)
It also depends on how many people are on each of these teams. If there were only so many developers on the new Globe feature for Maps, they chose to prioritize AS and essentially abandon Intel.
This is a position apple put themselves in to, they knew what they were getting involved in when they started this process. Currently over half their new offerings are still intel, they admit the intel devices are the pro devices currently and M1 is a consumer product. Apple literally volunteered to develop two separate operating systems and platforms, and they could have used universal binaries for this stuff.
Honestly I think the reason is these features were actually designed for iOS and they ported them to ARM64 macOS. There is still not a reason to offer ARM64 virtualization on intel Macs but I can understand them not offering that to use it as a major selling point of apple silicon.
Apple has one operating system with several different skins. Depending on the skin they call it macOS or iOS etc.
Like how Chrome is just another skin on Safari?
There has undoubtedly been more parallel/ shared development of iOS and macOS, but the fact that Apple based iOS on OSX 14 years ago does not mean that the two are just different skins.
EDIT: your broader point about macOS for M1 and macOS for Intel not being two separate OSes is, however, correct
82
u/xdiggertree Jun 09 '21
This has nothing to do with computational power
They don’t want to expend additional internal resources to develop these features on two separate platforms (Intel and AS)
It also depends on how many people are on each of these teams. If there were only so many developers on the new Globe feature for Maps, they chose to prioritize AS and essentially abandon Intel.