How it'd work - ARM SoC expands on what the T2 does today, except it now runs all system threads, any ARM native user space apps, and maybe specialty fixed func

How it'd work - ARM SoC expands on what the T2 does today, except it now runs all system threads, any ARM native user space apps, and maybe specialty fixed function blocks that Apple throws on those chips (e.g. media encode). Meanwhile the Intel chip is a co-processor for any x86 specific user space apps, and it otherwise doesn't touch drivers or any system things. That's not really Apple's style, at least not under Steve Jobs ;). You just throw the old architecture under the bus, provide some emulation to make Microsoft and Adobe catch up, all developers have to adapt and build fat binaries or get left behind. Apple can do this, since no one has a strong expectation of backwards compatibility anyway. Of course, ARM might not be competitive enough yet for Mac Pros. So they'll probably start with the MacBook Air or 12", require every developer that submits to the Mac App store to build universal binaries, and have some partners (probably Microsoft) that will provide support on day 1. For a chunk of the MacBook Air audience the architecture will be irrelevant, since they do Office, browse the web, and send e-mails. So, if they get a laptop with significantly better battery life doing that, it will sell. Once the Air has prepared the software market, go up the product line after 1-2 years. I like the Intel co-processor idea, but Intel CPUs are relatively expensive. So, they'd have to jack up prices, while going ARM directly would increase their margins at the same price points.