Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

UBS28

macrumors 68030
Original poster
Oct 2, 2012
2,893
2,340
Why not put the A14 or A15 from the iPhone in a MAC as well? The iPhone chip is powerful enough for most people and Apple could introduce an even thinner and smaller ultrabook laptop, the 11” MacBook?

I think it will sell really well, as the MacBook Air makes Apple the most money. So there is a clear preference for cheap devices.
 

JPack

macrumors G5
Mar 27, 2017
13,544
26,169
A14 doesn’t have a Thunderbolt controller and the memory bandwidth is half of M1.

Most importantly, the A14 chip isn’t much cheaper than M1 to manufacture. Based on the die size, it might be $30-40 cheaper. Using Apple’s typical 3X multiplier, Apple might charge $100 less at retail. Nobody will buy a MacBook without TB and half the memory bandwidth for $100 less.
 

Basic75

macrumors 68020
May 17, 2011
2,101
2,448
Europe
In addition to what @JPack said, they already sell truckloads of A14/A15 chips in iPhones and some iPads. The M1 is used in lower-volume products, but by using it in many of them they manage keep its volume up and cost down, too.
 

Apple Knowledge Navigator

macrumors 68040
Mar 28, 2010
3,692
12,912
M1 will be around for a long time I imagine. Despite being the first Apple Silicon for Mac and targeted towards consumer-orientated products, it still outperforms many Intel Mac counterparts. Apple could keep it around solely for an entry-level MacBook Air and I doubt anyone would complain.
 
  • Like
Reactions: Tagbert and yitwail

yitwail

macrumors 6502
Sep 4, 2011
427
479
Besides what's been mentioned, A14/A15 have fewer GPU cores and don't support an external display.
 
Last edited:

Sydde

macrumors 68030
Aug 17, 2009
2,563
7,061
IOKWARDI
Macs also have a lot more going on at any given time. iPhones lack windowing and are not designed to have apps running in the background (like doing a render while you are browsing websites). The 2x4 layout of phone chips is just not adequate for a computer workload.
 
  • Like
Reactions: Tagbert

theluggage

macrumors G3
Jul 29, 2011
8,015
8,449
Why not put the A14 or A15 from the iPhone in a MAC as well? The iPhone chip is powerful enough for most people and Apple could introduce an even thinner and smaller ultrabook laptop, the 11” MacBook?
Remember that the iPad Pro now uses an M1 - so Apple could easily produce an 11" MacBook, if they wanted, without "downgrading" it to an A15.

...and while I'm not arguing with the people who might want an 11" Air, I suspect that Apple's line would be that you should buy an iPad for that.

More interesting would be the ability to run MacOS on the (M1) iPad Pro.

Besides what's been mentioned, A14/A15 have fewer GPU cores and don't support an external display.

iPad (even pre-M1) supports an external display (hence the existence of this adaptor) for mirroring or media playback, independent of the main screen - so the hardware is quite capable of driving two displays, although iOS/iPad OS limits what you can do with them.

Macs also have a lot more going on at any given time. iPhones lack windowing and are not designed to have apps running in the background (like doing a render while you are browsing websites). The 2x4 layout of phone chips is just not adequate for a computer workload.

iOS/iPadOS is a fully multi-tasking operating system, and the iPad/iPhone rely heavily on background tasks to do what they do. iOS places artificial restrictions on how 3rd-party apps and the user can create background processes - but that is a software restriction - and one that has been slowly relaxed since the first iPhone, as mobile processors got vastly more powerful).

Let's be clear - there's no point in Apple making an A-series Mac when they could simply make an M1 Mac the size of the 11" Air (or a Mini the size of AppleTV) with much less compromise. However, it would be perfectly possible given that Apple have already done it in the shape of the Developer Transition Kit - an A12Z processor in a Mac Mini housing running MacOS. During the brief period for which Apple actually maintained support for it, and allowing for the fact that it was never destined to get out of "alpha", that did a perfectly credible job of running MacOS. Yes, there were restrictions - but you could say the same of the 12" MacBook in its day - (e.g. no Thunderbolt, and you probably wouldn't want to run a 4k display, multiple virtual machines or do heavy multitasking on that CPU/GPU, even if you could).

Some of the arguments here are reminiscent of the "why Apple will never switch to ARM" that seemed to suggest that ARM-based processors lacked some sort of secret sauce that "real computers" needed (...in complete denial of the benchmark results for the iPad Pro). Any processor that can cope with the iPad user interface is going to be good enough for an entry-level ultra-mobile.
 

yitwail

macrumors 6502
Sep 4, 2011
427
479
iPad (even pre-M1) supports an external display (hence the existence of this adaptor) for mirroring or media playback, independent of the main screen - so the hardware is quite capable of driving two displays, although iOS/iPad OS limits what you can do with them.
Good point, but A14/A15 doesn't support arbitrary content on an external display, whereas with M1 in MacBook Air or Pro, the external monitor can display content unrelated to the main screen.
 

Krevnik

macrumors 601
Sep 8, 2003
4,101
1,312
Good point, but A14/A15 doesn't support arbitrary content on an external display, whereas with M1 in MacBook Air or Pro, the external monitor can display content unrelated to the main screen.

First, that's not a hardware restriction. Second, it's not even really true.

At the hardware level, a display is a display is a display. If it can display content that is arbitrary enough for you is a platform restriction. Since iOS allows UIWindows to be associated with external displays, an app can display anything it wants on the second screen. The difference is that macOS has a window manager that manages all screens, while on iOS, screens are managed by apps, so apps are required to support multiple screens, while mirroring can be provided by the platform.

It's just very few if any apps on iOS support multiple screens. Even though Apple has an article on exactly how to do it: Displaying Content on a Connected Screen | Apple Developer Documentation
 
  • Like
Reactions: yitwail
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.