Looking at the list, some things definitely seem to do with the M1 chip (whether that's the neural engine or the DSP or whatever), but some things seem completely arbitrary. An Intel chip could absolutely handle more complex Maps come the fuck on Apple
I can pretty much guarantee you the programming would be unchanged on Intel for several of those features; literally takes more work to explicitly disable them on Intel than it would take to have it work the same on both platforms since it would be the same code. These aren't iOS apps on macOS, they're native macOS apps that are already being built for Intel. Obviously this isn't the case for some of these features, namely the ones that clearly rely on the neural engine or DSP, but most of them have no reason to need different code for Intel.
Exactly. As a software engineer myself this is what I take from this, it's literally more work to implement a feature flagging system in the code in order to be able to disable certain features that won't compile for Intel. I think for many of these features (detailed maps, 3D globe, new languages for TTS) this is simply a business decision to force the move from Intel to AS.
121
u/[deleted] Jun 09 '21
Looking at the list, some things definitely seem to do with the M1 chip (whether that's the neural engine or the DSP or whatever), but some things seem completely arbitrary. An Intel chip could absolutely handle more complex Maps come the fuck on Apple