Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
However, the question was ”Does anyone know if this will affect Bootcamp?” and no one does.
... The rumour as claimed is that Macs will drop Intel processors and adopt Arm processors.

That will affect Bootcamp - the feature allowing a Mac user to boot into a regular Windows environment. We can't say how it will affect it - because maybe the support will change to Windows on Arm. Maybe it'll go away. But without an Intel processor, maintaining the status quo is impossible, and thus yes, we do know that this would without any question, affect Bootcamp.
 
I see an ARM switch as conflicting with some of Apple's recent moves. They came out with the iMac Pro, then the Mac Pro and XDR display. All of these are targeted at the "pro" market, which need strong horsepower and app support. As it stands, ARM simply cannot put out the power that these machines can.

They almost certainly wouldn't start on the high end, yes.

(Although, to advocate for the counterpoint: it's on the high end that Intel currently doesn't have a good story. Ice Lake-Y and -U have saved low- to mid-end laptops, but with 45W and beyond, their current chips are quite mediocre, with no fix in sight for another two years. Comet Lake won't fix it. Rocket Lake after that won't fix it.

Now, Ice Lake-SP should, and maybe we'll see that one trickle down to the iMac Pro and Mac Pro next year. We'll see.)

Now, the rumor has it that this will start at the low-end, with MacBooks. This will present a huge mess, if they are planning to transition over the course of multiple years. They'll have to built 10.16/10.17 on x86 and ARM, as both will be current products. This is just going to make the buggy state of the OS even worse. App developers will also be in a weird spot, having to build universal apps again. Sure, it can be done, but some won't find the extra effort worthwhile.

I really don't see this as a problem. This would be one of many times Apple has done fat binaries. They had 68k+PPC binaries in the 90s, PPC+x86 binaries in the 00s, and even PPC+PPC64+x86+x86_64 binaries in the 00s.

They almost certainly have internal builds of macOS running on various architectures. I would bet there are prototype builds of it running on RISC-V, even — just in case Apple wants to save some money on that ARM license.
 
Well, they almost certainly use BTO upgrades to subsidizes items with lower margins.

Something like maybe a 10-15% margin on the iPad Pro LiDAR, and some of the AirPods components — but then a 40%+ margin on BTO upgrades (and probably more like 75% on the RAM in particular, TBH).
Yeah, it’s an overall target gross profit margin; around 32% for hardware.

Especially within a product line, upgrade pricing subsidizes the base price. Overall that was the point I was trying to make. The reason you can have a $1,299 base price 13” MBP is because the 8G upgrade is $200. (And SSD upgrades are similarly high priced.)

OP wants a 16GB base model because he thinks he can get it for the $30 difference in the component pricing between 8 and 16GB. That’s not how it works.
 
I predict that in the first few years of its introduction, new ARM based processors will be a major failure for Apple causing them to loose most of their 10 percent share of the pc market. The reason is that initially a lot of software will be incompatible and just won't work on the new processors (at least for the first few years). The second reason is that there will no longer be the option to dual boot OSX with Windows as Windows won't be compatible. The only saving grace for arm based processors is if the speed majorly outperforms Intel chips and if the cost of chipsets is reduced.
 
It turns out Intel is probably underestimating the power consumption of their CPUs (or at least not defining TDP in the same way as I defined it to rate the A12X).

Using the same method (tests are performed by the same online magazine while reviewing the MacBook Pro 13-inch 2019)...

View attachment 901948

It turns out that the 28W CPU in the MacBook Pro 13-inch (Intel i5-8279U) actually consumes much more than we expected.

Using the same formula as we used to estimate the A12X power consumption (minus the standby because when a Mac is in standby the CPU is actually not powered) ...

Load Maximum - Idle Average = 63.9W - 7.2W = 56.7W !!

Even if you account for the consumption of the separate RAM modules (which in the case of the A12X are part of the CPU) you are left with at least 45W of power consumed by the CPU alone. A 28W Intel CPU actually consumes around 45W on full load.

So here you have it. Final comparison: A12X consumes 7W while delivering the same performance of the Intel CPU that consumes around 45W (if not more). A12X is around 6 times more efficient than Intel processors currently inside MacBook Pros.

The more we dig into details, the more my initial figures look conservative. The new MacBooks will FLY when executing apps recompiled for ARM and they will be possibly even marginally faster than current MacBooks when executing x86 apps.

Screen Shot 2020-02-21 at 7.49.41 PM.png
Screen Shot 2020-02-21 at 7.49.33 PM.png


Yup, 9980HK consume 90~135W in real life.
 
This is for a distributed key store, which is highly parallel in nature, a very different workload from what you'd run on a Mac. People use Intel and AMD in mid-to-high end personal computers, where there's not even an ARM CPU to compare to. If there were and it were comparable or even faster, that wouldn't surprise me, but there's no data.

Geekbench, Anandtech 's article. Along with AWS Numbers. Apple A13 Single Thread Performance. All of these are Data. You pointed to KeyDB as if Single Thread Performance doesn't matter in KeyDB and other DB while ignoring all others. There are number of company running their software on M6g at this moment.
 
I predict that in the first few years of its introduction, new ARM based processors will be a major failure for Apple causing them to loose most of their 10 percent share of the pc market. The reason is that initially a lot of software will be incompatible and just won't work on the new processors (at least for the first few years). The second reason is that there will no longer be the option to dual boot OSX with Windows as Windows won't be compatible. The only saving grace for arm based processors is if the speed majorly outperforms Intel chips and if the cost of chipsets is reduced.

1) people who really want windows buy a windows machine. Apple can’t base its strategy on windows. And windows-on-mac is a small portion of mac users.

2) there will initially be MUCH MORE software compatible with ARM mac, because it will be able to run most iPadOS and iOS software natively. There are orders of magnitude more of such software than is currently available for the mac.
 
Geekbench, Anandtech 's article. Along with AWS Numbers. Apple A13 Single Thread Performance. All of these are Data. You pointed to KeyDB as if Single Thread Performance doesn't matter in KeyDB and other DB while ignoring all others. There are number of company running their software on M6g at this moment.

It's not clear what point you're trying to make. Amazon's chips are for very different workloads than Apple's. Apple is focused on (and good at) single-core performance because that matters a ton; for the most part, JavaScript is limited to a singlt thread (yes, I know about workers), for example. Getting parallelism to make sense in general-purpose apps is also hard.

In contrast, Amazon is doing this for apps that are highly specialized.
 
I mean, cool, but this story is about ARM-based Macs (assuming they are a thing), and as long as Apple can charge millions of people $200 for 8 GB of RAM, and those people happily buy, they will continue to do so.

My point was that some people are excited about an ARM Mac, but they should more be excited about an extra bump in ram and storage IMHO
 
2) there will initially be MUCH MORE software compatible with ARM mac, because it will be able to run most iPadOS and iOS software natively. There are orders of magnitude more of such software than is currently available for the mac.

I really don't see the basis for this assertion. Yes, Catalyst is a thing, but a Catalyst app on a Mac is an awful experience (just try launching Home), and changing CPU architectures isn't going to change that.
 
1) people who really want windows buy a windows machine. Apple can’t base its strategy on windows. And windows-on-mac is a small portion of mac users.

2) there will initially be MUCH MORE software compatible with ARM mac, because it will be able to run most iPadOS and iOS software natively. There are orders of magnitude more of such software than is currently available for the mac.

A lot of those who runs Windows on Mac do this because of Windows only software, not because they prefer Windows

x86 are 100% able to emulate ARM, the proof of this is that iOS app are often build inside xCode simulator
 
I really don't see the basis for this assertion. Yes, Catalyst is a thing, but a Catalyst app on a Mac is an awful experience (just try launching Home), and changing CPU architectures isn't going to change that.

Give it time. They just now added keypress events and indirect pointer support to iPadOS. As iPadOS apps are updated to support keyboards and trackpads, those apps will work much better in catalyst. They have also been adding additional catalyst capabilities over the last couple of OS releases, so it will all get better.
 
A lot of those who runs Windows on Mac do this because of Windows only software, not because they prefer Windows

x86 are 100% able to emulate ARM, the proof of this is that iOS app are often build inside xCode simulator

Again, apple doesn’t really care about Windows on mac people anymore. They needed to a decade ago. Now they don’t.

Of course x86 can emulate Arm, but that’s not what the simulator does. When you build for the simulator it builds an x8–64 package.

Anyway, Arm is technically superior to x86, so Apple switching to it will be good.
 
It's not clear what point you're trying to make. Amazon's chips are for very different workloads than Apple's. Apple is focused on (and good at) single-core performance because that matters a ton; for the most part, JavaScript is limited to a singlt thread (yes, I know about workers), for example. Getting parallelism to make sense in general-purpose apps is also hard.

In contrast, Amazon is doing this for apps that are highly specialized.

I was replying to the point is we have ample of evidence that ARM can be and are already competitive to x86. And yet people constantly say otherwise. There is nothing different about work load on an N1 ARM than a x86 Desktop CPU other than the AWS CPU has many more core. It doesn't even offer SMT like Marvell's implementation of ARM on Server. And Apple has already shown their ARM chip perform faster in iPadOS / iOS Safari compared to Safari on x86 Mac.

People might not like ARM on Mac, That is Fine.
People might not agree ARM on Mac makes sense, That is Fine.
People might not think ARM on Mac makes financial sense, That is Fine.

I absolutely accept we may agree to disagree on opinions.

But suggesting ARM has not proved to be as fast as x86 now ( and in some cases will never be made as fast as x86 ), is misinformation at best, disinformation at worst.
 
Last edited:
Give it time. They just now added keypress events and indirect pointer support to iPadOS.

They did, but they also went through a lot of effort to make those iPadOS pointers not look and feel like macOS or Windows pointers.

Which, yes, still helps Catalyst on macOS. But right now, Catalyst is pretty mediocre, has launched way prematurely, and Apple's own apps are mostly bad (one exception being Podcasts).

As iPadOS apps are updated to support keyboards and trackpads, those apps will work much better in catalyst. They have also been adding additional catalyst capabilities over the last couple of OS releases, so it will all get better.

It will.

The other shoe that needs to drop for your assertion, though, is for app devs to care. Unless you're arguing that Apple will eventually force their hand and put iOS apps in the Mac App Store without the dev's input.
[automerge]1585416448[/automerge]
A lot of those who runs Windows on Mac do this because of Windows only software, not because they prefer Windows

x86 are 100% able to emulate ARM, the proof of this is that iOS app are often build inside xCode simulator

The iOS Simulator is called a simulator because it's not an emulator. iOS apps that run in the simulator are actually x86, not ARM.
 
  • Like
Reactions: fairuz
I was replying to the point is we have ample of evidence that ARM could be and are already competitive to x86.

Kind of? But Amazon's CPUs don't add to the evidence. They're completely irrelevant.

It's like taking Xeon Phi and saying "see? here's proof x86 can scale to 72 cores!" Which, yes, Xeon Phi is x86, but is otherwise is misleading.

And yet people constantly say otherwise. There is nothing different about work load on an N1 ARM than a x86 Desktop CPU other than the AWS CPU has many more core.

No. The workload on an N1 is extremely different than on an x86 desktop. Or any desktop.

And Apple has already shown their ARM chip perform faster in iPadOS / iOS Safari compared to Safari on x86 Mac.

Maybe, but that's not really the point you were making.
 
  • Like
Reactions: fairuz
Again, apple doesn’t really care about Windows on mac people anymore. They needed to a decade ago. Now they don’t.

Of course x86 can emulate Arm, but that’s not what the simulator does. When you build for the simulator it builds an x8–64 package.

Anyway, Arm is technically superior to x86, so Apple switching to it will be good.

No, lot of peoples do care and I think Apple too, especially if you work for a company with a Windows only internal software

You are right, but ARM emulator exist and run smoothly

no ARM is not superior, not at all
[automerge]1585416615[/automerge]
The iOS simulator doesn’t emulate arm, Xcode builds the iOS app for x86.
You are right, my fault
by arm emulator exist for x86, especially Android emulator and they run smoothly
 
As iPadOS apps are updated to support keyboards and trackpads, those apps will work much better in catalyst. They have also been adding additional catalyst capabilities over the last couple of OS releases, so it will all get better.

Catalyst isn’t a magic “deploy on macOS” button. Your assertion is that most iOS/iPadOS will be available - but catalyst is available already and yet no flourish of catalyst apps on Mac - and the issue is unrelated to the cpu architecture.

Why do you keep repeating this same ridiculous claim?
 
Kind of? But Amazon's CPUs don't add to the evidence. They're completely irrelevant.

It's like taking Xeon Phi and saying "see? here's proof x86 can scale to 72 cores!" Which, yes, Xeon Phi is x86, but is otherwise is misleading.



No. The workload on an N1 is extremely different than on an x86 desktop. Or any desktop.



Maybe, but that's not really the point you were making.

Xeon Phi performers poorly in single thread performance, Which makes your point moot.

Workload is software dependent. That is nothing Hardware about work load. That is not even the correct terms to use in the first place. You could have ran Handbrake on the N1, Photoshop on the N1. SPEC on the N1. If you dont understand what Anandtech were testing then there is aboustely no point in further discussing.
 
Xeon Phi performers poorly in single thread performance,

So does Amazon N1.

Workload is software dependent. That is nothing Hardware about work load. That is not even the correct terms to use in the first place. You could have ran Handbrake on the N1, Photoshop on the N1. SPEC on the N1. If you dont understand what Anandtech were testing then there is aboustely no point in further discussing.

So you concede that using N1 to make any point about mobile or desktop CPUs didn't make any sense.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.