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...
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.