It will simplify MacOS when they end Intel support.
Not only a cost to Apple, but also a cost to 3rd party Mac developers, who would be even less likely to have the resources to support the Mac Pro for its own sake.
Apple dropped PowerPC support in Mac OS X (10.6) 3.5 years after the Intel transition started, and they dropped Rosetta support in Mac OS X (10.7) 2 years after that.
IIRC the last PPC Mac hardware was discontinued very soon after the Intel transition started.
Anyway, no, not for Apple either, because Mac Pro unit sales are already low, and trying to make that one Mac model cover the cost of all macOS Intel support will make the already expensive and low volume Mac Pro even more expensive, and thus even lower volume, making it harder to cover the cost.
The question is how they will pay for a high-end chip when they no longer can rely on Intel to spread out the development cost among many customers.
Frustrating those people likely comes with a risk of losing high value customers.
I think it’s similar to the model a lot of game consoles have. They make little to negative profit on the console itself during the first couple years, but make it up on software and other benefits of hardware lock-in.
In the time after the trashcan Mac Pro they lost a significant portion of the professional market. And while that market is relatively small, it's highly influencial.
By the time Final Cut Pro X was unveiled Apple could boast that 60% of Hollywood movies are edited on a Mac. Now? Not so much. And this probably extends into other areas, too.
There was no version 9, nor version 8. ;)
The difference would be supporting Intel publicly - with third-party developers. As the target for Mac Pros won't just be running a load of electron apps.
Which is the question I have been asking since 2015. From a cost prospective it never made any sense. Presumably they will wait until Mac Studio becoming powerful enough to fill the gap.
>but the Mac Pro seems to be a clear case where using a powerful off-the-shelf Intel chip makes more business sense right now.
It surely does. Except it will be the only Mac in the lineup without Metal Support and Apple's increasingly important NPU for Machine Learning features. I dont see it as a good trade off.
To me the only reason they still make products like the Mac Pro is for brand reputation and face-saving. It’s like when a big auto maker sponsors a formula 1 racing team. There’s no profit in formula 1 (for the auto makers). It’s just a giant money pit!
If I'm starting out today and looking to choose a PC or Mac ecosystem, if I see that the Mac has an upper bound that's lower than the PC, then in my starry-eyed optimism as a newbie I'll think I might as well start as the PC since one day when I'm super successful and I need more power I'm going to have to change platforms anyway.
Even if none of those users will ever end up using any more power than the Mac Studio, if they're convinced they will then they will not choose your ecosystem.
Some caveats:
* maybe not true if you go back to the introduction of metal but idk
* metal feature support varies by hardware
> The Metal framework gives your app direct access to a device’s graphics processing unit (GPU).
I’m not sure how to respond as a result since it’s hard to discuss in good faith.
V1 of their comment simply asked what “metal” evokes in one’s mind.
V2 then posted a link to the Metal page saying it lets you directly use your GPU hardware.
V3 is now pointing out that metal feature support varies by hardware which I already called out, but they’re positing as a contradiction somehow.
As such I’ve removed my reply because it makes no sense based on their frequent changes and left this one instead.
As for your latest update, I had already mentioned that in my comment as a caveat, though I hadn’t shared the link which is always great to have.
The two tricky things I'd anticipate are:
What does it look like to hardware? Different CPUs speak different protocols to maintain a cache coherent view of memory. So they couldn't easily share memory in a completely natural way - but GPUs manage to share memory between host and GPU, so it can be done (just not necessarily as conveniently to software).
What does it look like to software? Lots of weird options here. Most convenient for software compatibility is it the Intel is also somehow running MacOS (or appears to be). I guess you could do that - it'd be like having a two node cluster in one machine. But that's not as convenient as being able to distribute computation between compatible CPUs.
None of that is a complete technical blocker to a company that controls their stack, I'd just guess it would make it too inconvenient / expensive for them to do.
That said - as an intern, years ago, I once had access to a piece of prototype hardware that had an x86 chip in one motherboard CPU socket and a non-x86 chip in the other (with various adaptation hardware to allow them to play nice). I think that was more a proof of concept than anything else, not necessarily viable without other hardware changes. Interesting nonetheless.
I saw a lot of new-in-box examples cheap on eBay prior to Sun's implosion, so I suspect they weren't particularly popular and were primarily targeted at a few important customers that had some box to tick.
Eg: https://everymac.com/systems/apple/mac_quadra/specs/mac_quad...
That is until you run the calculation when the cost of doing it are in the tens of thousands per unit. Suddenly it doesn't make much sense.
Sure, Threadripper makes economical sense for AMD only when "subsidised" by EPYC/Ryzen sales and the shared chiplet architecture. But Apple has deep enough pockets for halo products. They are allegedly repurposing some of the binned/sub-par silicon into internal server hardware anyway.
In their own datacentres?
AWS is already doing so with Graviton.
It has nothing to do with macOS.
Graviton CPUs are not for sale. If Apple wants a million ARM cores to run iCloud, they are going to have to get TSMC to fab them.
They can probably heavily base a more powerful chip on their existing designs but with more cores & cache, so design should be relatively cheap. Manufacturing the masks etc. is probably around $10m which is probably fine given how expensive Mac Pros are (and it would simplify their software if they can ditch Intel entirely).
Somebody buying a mac pro would probably expect support for discrete and expandable ram.
Maybe it needs more PCIe lanes but again that probably doesn't need much design work.
They are not starting from scratch. The Apple Silicon MX chips all share a common base, and are related to the AX chips. When every product Apple sells is using some version of the same family of chips, a lot of the design cost is spread across all Apple devices.
Then it's just the incremental design cost that must be recouped for things like (speculated) off die RAM.
Most of the M-series chips are shared across multiple products, but the Mac Pro seems to be a clear case where using a powerful off-the-shelf Intel chip makes more business sense right now.
I don’t see Apple doing it simply as a vanity project, so there will have to be some innovation or new product line coming if an Apple Silicon Mac Pro is to ever exist.