Apple announces it will switch to its own processors for future Macs
theverge.com
theverge.com
Current A12z chips are highly performant; Apple is roughly one chip cycle ahead on perfomance/watt from any other manufacturer. I presume their consumer hardware will launch with an A13Z, or maybe an A14 type chip.
Apple has consistently shipped new chip designs on time; Intel’s thrashing has cost them at least two significant update cycles on the macbook line in the last six years. Search this fine site for complaints about how new mac laptops don’t have real performance benefits over old ones —- those complaints are 100% down to being saddled with Intel.
Apple has a functional corporate culture that ships; adding complete control of the hardware stack in is going to make for better products, full stop.
Apple has to pay Intel and AMD profit margins for their mac systems. They are going to be able to put this margin back into a combination of profit and tech budget as they choose. Early days they are likely to plow all this back into performance, a win for consumers.
So, I’m predicting an MBP 13 - 16 range with an extra three hours of battery life+, and 20-30% faster. Alternately a Macbook Air type with 16 hours plus strong 4k performance. You’re not going to want an Intel mac even as of January of 2021, unless you have a very unusual set of requirements.
I think they may also start making a real push on the ML side in the next year, which will be very interesting; it’s exciting to imagine what Apple’s fully vertically integrated company could do controlling hardware, OS and ML stack.
One interesting question I think is outstanding - from parsing the video carefully, it seems to me that devs are going to want ARM linux virtualized, vs AMD64. I’m not highly conversant with ARM linux, but in my mind I imagine it’s still largely a second class citizen — I wonder if systems developers will get on board, deal with slower / higher battery draw intel virtualization, or move on from Apple.
Languages like Go with supremely simple cross architecture support might get a boost here. Rust seems behind on ARM, for instance; I bet that will change in the next year or two. I don’t imagine that developing Intel server binaries on an ARM laptop with Rust will be pleasant.
I'm predicting the opposite: you won't actually see any difference.
Once you look closely at power profiles on modern machines you'll see that most energy is going into display and GPU. CPUs mostly run idle. Even if you had a theoretical CPU using zero energy, most people are not going to get 30% battery life gains [1]. Not one thing that they demoed requires any meaningful CPU power.
Similarly, while ARM parts are more efficient than x86 per compute cycle, it's not a dramatic change.
The big changes, I think, are more mundane:
- Apple is going to save $200-$800 cost per Mac shipped
- Apple can start leaning on their specialized ML cores and accelerators. They will probably put that stuff in T2 for Intel Macs. If they're already shipping T2 on every machine, with a bunch of CPU cores, why not just make those CPU cores big enough for the main workload?
Doubling CPU perf is meaningless if you can ship the right accelerators that'll do 100x energy/perf for video compression, crypto and graphics.
[1] for a regular web browsing type user; obviously if you're compiling stuff this may not apply; if that is true you're almost certainly better off just getting a Linux desktop for the heavy lifting
There is no guarantee that a phone-scale CPU can just become 4x faster by 4x'ing the power/TDP/die area. If it were that easy, Intel would already have done it (and no, the x86 architecture isn't so terribly inefficient that they are leaving triple-digit percentage improvements on the table).
What I expect we'll see are ARM chips that are power and performance competitive with x86 chips only for specific curated use cases. Apple will extract an advantage by putting custom hardware acceleration into them, to cater for those specific tasks. They will not be able to achieve general purpose performance improvements wildly beyond what Intel can already do.
This is how the current iDevices achieve their excellent performance and battery life. Not through raw general-purpose CPU horsepower, but by a finely tuned synergy between hardware and software. Apple are taking their desktop down the same route. This will be the ultimate competitive advantage for their own software - they will be able to move key software components into hardware, and make it look like magic. But as a developer, you won't be able to participate in this unless you target Apple-blessed hardware instructions/APIs. Your Python script isn't going to start running 4x faster unless you can convince Apple to implement its inner loop in custom silicon.
I have no doubt that Apple will be leaning hard into ASIC territory as they build out their new CPUs. The endgame? Every software function you need, baked into perfectly optimised silicon by the monovendor.
Eh? This is a flimsy claim. AMD's performance/watt is extremely impressive right now. Apple is ahead of Intel for sure, but Intel isn't the only other player here.
> So, I’m predicting an MBP 13 - 16 range with an extra three hours of battery life+, and 20-30% faster. Alternately a Macbook Air type with 16 hours plus strong 4k performance.
A slightly more efficient CPU doesn't get you this. You need significant efficiency improvements across a variety of aspects, including those Apple has already been optimizing for years like the display.
I saw speculation elsewhere that this change, along with AWS's addition of Graviton-based (their own ARM processors) instances at much more competitive price points relative to x86, are bound to spearhead the change to "ARM by default."
If your devs are already using ARM, and ARM's notably cheaper in the cloud, that's a compelling case. If you're already using Kubernetes / Docker heavily, you're probably already 80% of the way there. Linuxes that aren't supporting ARM as a "first class citizen" will soon, and undoubtedly that will be a speed bump at worst.
I'm interested to see the specs relative to the x86 Macs, but the only open question to me was whether or not we'd see the x86 emulation layer. Well, we did, and it may not be perfect but it certainly looks like they put a lot of effort into it. If it works as well as it looks, I think this transition is borderline inevitable. I think I've bought my last x86 hardware.
Take for example the A12Z. It has 8MB of L2 (not L3, it's L2!) cache. An Intel Core i7-1068NG7 present in the latest Macbook Pros (that performs akin to the A12Z according to Geekbench) has only 2MB of L2 cache.
No other ARM CPU has this level of L2 cache. Apple chips are not "magical", Apple just can afford packing up lots and lots of cache because they are not in the silicon "race to the bottom" like Qualcomm and Intel are, for example. L2 cache is very expensive and Apple is just hacking its way up by packing as much L2 cache as they can.
Don't take me wrong, it's not that Apple is "right" or "wrong" by doing it. They just can and did it. However, it's needless to say that their CPUs are not so different from other ARM ones, they just happen to have a budget and a business model that let's them ignore the price/performance ratio when designing chips in order to achieve the maximum performance.
> Current A12z chips are highly performant; Apple is
> roughly one chip cycle ahead on perfomance/watt from
> any other manufacturer.
We haven't been able to compare them. Micro-benchmarks do not count because mobile versions of Apple chips haven't been designed for desktop requirements. People love comparing CPU cores with micro-benchmarks, but the hardest thing for a modern desktop/server chip is to feed data to many cores while maintaining cache coherence. > So, I’m predicting an MBP 13 - 16 range with an
> extra three hours of battery life+, and 20-30% faster.
Before agreeing with your estimates, I want to play with a true 8-core Apple CPU with a large multi-level cache first. Building the Linux kernel with -J16 will be a fun exercise. Look, AMD is not stupid, and they're on the same node Apple will be using, and they're not 30% faster than even a 5y.o. Skylake. > Apple has to pay Intel and AMD profit margins for
> their mac systems. They are going to be able to put
> this margin back into a combination of profit and
> tech budget as they choose.
I wonder how their conversations with TSMC go. With Intel, at least they had AMD to use as a bargaining chip. With TSMC there's no alternative. > One interesting question I think is outstanding -
> from parsing the video carefully, it seems to me
> that devs are going to want ARM linux virtualized
> vs AMD64.
That's the big one. The world's software is built for and runs in data centers, not laptops. Our machines are increasingly becoming nothing but thin clients, remote displays that happen to run Javascript. CPUs do not matter. And I suspect that's the real reason they're switching.But from the developers perspective, it's incredibly convenient to use the same platform (OS + instruction set) as the machine they're targeting, even for interpreted languages. Linus Torvalds wrote a well-articulated email about this a while ago, IIRC he was commenting on POWER, but I think his points are valid. At my company, devs keep struggling with Docker on a Mac. Add to that the ARM pain, and I wonder how many will finally get a Thinkpad. Developers will switch to ARM when majority of AWS instance types goes ARM.
P.S. I love how "old-tech" HN is, but for the love of god, give us a decent way to "reply with quote".
Apple has an absolutely top-shelf team, designing chips.
By hand (Qualifier: Not sure if they still do, but they did, while everyone else was using automation).
They also have a great deal of experience in repaving the highway while traffic is running at capacity. They mentioned it in their keynote. They've done it three times. I have been there, for each of those times.
I was also there for the one time they completely pooched it (Can anyone say "Copeland"? Drop and give me twenty!).
It will be moderately painful. Not too bad. Quite manageable, and it will take at least a couple of years to transition.
I am in no hurry for one of those dev kits, though. They will be quite rough, and I have no compelling reason to use them.
I am looking forward to an entirely new Xcode. The current one is getting crashier every day. I'd also like to have one that can run on my iPad.
Go does have the (platform) advantage (?) of preferring the "rewrite everything in Go" approach, so those just transition when the tooling supports a new architecture. Rust is intentionally going with a interop design, rather than telling people the only answer to to rewrite all their favorite libraries.
IMO ARM linux is great, the real thing lacking is good hardware to run it.
In terms of distros maybe yes. Most distros are targeted at laptops, desktops or servers, and few of those have ARM processors.
In terms of architectural support by the kernel and low-level infra, I see no reason for that to be true at all. Open source kernels and (at least lower-level) userspace have for decades paid more attention to compatibility with various hardware architectures than proprietary operating systems.
Of course you'll have fewer drivers for hardware associated with a particular architecture if there's less interest for the hardware, or if the hardware is less available in form factors that most developers are interested in. But that applies at least equally to non-open source platforms. If MS or Apple don't have a commercial interest in maintaining support for a particular platform (and they usually have only one or two in mind), nobody's going to do it.
They are going about expanding its marketshare.
There are close to 1 Billion iPhone users, most of them have never used a Mac. We will need a 2nd Devices for some of those task. And that will either be a iPad or Mac. Out of the 1.5B total PC Market, Apple has 100M Mac users. I will say it is not too far fetched to say Apple wants to double the number of Mac users to 200M.
For every $100 dollar going to Intel, Apple could knock $200 off its Retail price while getting the same margin.
A $799 MacBook ( the same starting price of iPad Pro ) will be disruptive, the premium is now small enough over the ~$500 PC Notebook price.
In the longer term I think Apple is trying to reach 2 Billion Active Devices. And it certainly cant do this with iPhone alone. There are plenty of Market Space for the Mac to disrupt.
I just want to plug in an eGPU to an RTX 2080 card. Instead, you have this incredibly limited set of officially supported cards the are also hyper expensive. Black Magic stopped making their eGPU Pro, so even if money is no object you can't get a great laptop GPU extension that supports their XDR displays.
Now, you might be saying, if you want a great GPU why are buying a laptop? Well, 1) even if I were to get the one model of Mac that allows me to do something interesting with GPUs (Mac Pro), I still can't install the NVIDIA cards I want. And 2) laptop + great eGPU is a great setup that is supported in the non-Mac space, so it is not a bizarre request.
All of this to say: the ARM stuff is fine, but it won't really move the needle for me, and doesn't address any of my performance issues, and I would argue a lot of the performance issues a lot of people actually have (especially graphics artists).
And yet the new Macbook pro base models feature an 8th Gen Core i5. That is 2 generations behind the bleeding edge. I think some people might be experiencing the speed problems you described because their machine has an old gen processor in a shiny new box
It's in fairly good shape, and has an active community. With the current proliferation of IoT devices, both the kernel and userland are well-maintained, and plenty of distros are available. The kernel also benefits from much of the work done for Android and Chromebooks as well.
All of the usual FOSS software is ported and runs well. As of this moment, you could easily take your pick from any of Debian, Ubuntu, Fedora, Arch, Manjaro, Slack, or Alpine just for starters, plus a whole mess of specialty distros. Many of those offer both 32- and 64-bit ARM versions.
Also bear in mind that recent ARM CPUs do support hardware-assisted virtualization as well. KVM and Xen are both available for ARM today, and I'd be shocked if Apple's Hypervisor.framework doesn't roll out with ARM support in the new macOS version as well.
(I'm writing this from Firefox in Manjaro ARM on a PineBook Pro, that I use as my daily driver)
So true! But from a market dominance perspective, it's also a bit terrifying.
Somewhat ironically, I think it's mostly the languages trying to be safer alternatives to C that are most behind on supporting ARM.
I've done a little bit of Lisp development on my Raspberry Pi (with SBCL and Emacs/Slime), and in most cases I don't have to change anything moving between my AMD64/Linux desktop, Intel/OSX MBP, and ARM64/Linux Raspberry Pi. And that's even when using CFFI bindings to C libraries.
I'm not sure SBCL's ARM backend is at the same level as the x86 backends, but it works well, and there's on going work on it.
Hahaha, look for a user-agent at 1:44:26 :) They use old Intel Mac for a virtualization demo.
I still major advantages of putting a A-series chip into a MacBook Pro.
1) There will be a much larger thermal and power draw envelope available to new A-series chip. I suspect we will see insane “boosting” clock speeds.
2) Incredible “at idle” performance well beyond what X86 can provide with on did GPU cores, which means a bit better battery life for that screen.
3) More opportunity for tightly integrated acceleration chips On die for codec, ML, and other hardware acceleration methods for Apple only software libraries.
4) Easy porting between iOS and macOS, and tvOS.
#3 will be the most significant.
Umm what? Rust supports ARM as a first class citizen as does LLVM. They only list ARM as second class because it's not a desktop platform generally. https://forge.rust-lang.org/release/platform-support.html
About the virtualization, they will probably make it more efficient, resource wise? Some cloud providers are also offering ARM so...
Anxious to check the GPU performance too!
To add: Control Center on macOS and some other UI improvements hints for Mac w/ touchscreen?
Could we finally see a true BYOD, like Dex or using the improvements in Handoff?
Go's crypto libraries are heavily optimized on x86, not so on arm (see Phoronix Graviton2 benches).
We will have to wait and see how much of Apple's halo effect will contribute positively to optimized arm code.
One word, Catalina.
Well we've already seen things gets delayed and even canceled (AirPower).
Cook's Apple is more about supply chain (where he excels), so if indeed the silicon design works, they would be able to 'ship'.
I predict they'll have the same battery life. Any savings will be used to reduce the battery size.
Microsoft is working on Office updates for the new Mac silicon, and Word and Excel are already running natively on the new Mac processors, with PowerPoint even using Apple’s Metal tech for rendering. Apple has also been working with Adobe to get these pro apps up and running on these new chips.“
So the bottom line is: “your previous tools won’t work, will have to be rewritten, the burden is on the developers so we can rake in more cash”
Great, customer focused, and completely altruistic move back in the days when they killed Nvidia cards on high-performance rendering and simulation machines (and everywhere else).
So, Apple has performance libraries that are better than what Intel has to offer? So, cross-platform applications are now again “passe”?
I don’t use my iPhone for working. Why would I want iOS Apps on my computer? So I can install Apple Mail instead of Outlook
That reads to me Apple isn't going to have Intel for some high end Pro machine. They intended to go all in with ARM. i.e There will be a Mac Pro with High TDP ARM Chip. I wonder what are the owner of Mac Pro feeling now having just spend a $5K+ Mac Pro with Intel.
Question is,
1. They are going to design their own CPU for the whole range of Mac? up to 10W for MacBook, up to 45W for MacBook Pro. ~150W for iMac, ~ 250W for Mac Pro ? How is that financially feasible considering the volume of Mac Pro sold. Or do they intend to use those high TDP chip in their server farm / iCloud?
2. What happens to GPU? Having their own GPU for iMac and Mac Pro as well? Dual GPU options where Apple GPU for power efficiency? This feels like additional complexity.
3. Would it be like the PowerPC era where you will get a new iMac once you finish with the development kit?
Finally while I am excited for ARM Mac, at the same time I am also feeling a little sad. Good bye x86.
I think GPU scaling will be much harder than CPU, so whereas Apple can surpass Intel CPUs for all but the highest segments, putting together a standalone GPU will be hard and very interesting to see. For an entry-level GPU? No issues. But what about a midrange (AMD RX 5700XT or Nvidia 2070S)? And not to mention the top-tier Nvidia 2080ti.
The other unspoken risk is that while Apple may be vertically integrating its SOC, it still relies on a fab like TSMC. Intel's recent problem is rooted in their inability to move off legacy 14nm fabrication process. TSMC may have done great in 7nm and now to 5nm transition, but what happens if/when they stumble? Would Apple also want to acquire them or build its own fabs to mitigate this risk?
Did it do any CPU-intensive stuff (skinning, deformation), or was it just GPU-intensive viewing?
High-end VFX will be interesting for this with Apple (Maya, Houdini, Nuke) - already there was quite a lot of anger at OpenGL being deprecated and Vulcan not being officially supported. Another instruction set into the mix for highly-optimised apps (lots of SIMD code) is going to be quite annoying, especially for the CPU renderers (Arnold, Renderman, etc)...
Logic isn't worth much without plugins, and I expect many smaller developers not to port to ARM, and there's nobody to fill the gap in the first years. If that is indeed the case, Apple will begin losing market share where it currently reigns. When there's no pro software, the mac will be just an iPad with a keyboard. It's quite a gamble.
But I've been too pessimistic before.
Not much. If you bought that machine you didn't care about it much as you bought older hardware at a premium price-point. You bought it to use it right now without fussing and have accepted it's obsolescence in 2-4 years, as is quite normal for studios.
If you bought it as an IT enthousiast, well..why would you even do that?
I don't see Apple coming out with an ARM Mac Pro within 3 years anyway. Why would they do that? No upside for them, that market has to be won back first. Slowly start with laptops and iMac, focusing on consumers, get the OS in shape and third-party vendors accustomed to the platform first.
iPad-like performance is already fast enough for almost all consumers, and I'm sure Apple doesn't want to break with Intel on everything right away.
I think it's a more common problem to see things like the T2 security chip not being present on older hardware or hackintosh(unsupported) hardware, so if you're not running the right hardware you can't take advantage of a feature (AR in certain iPhones) or you won't have the performance advantage (Filevault encryption with T2 chips vs encrypted by CPU).
2. They're saying integrated. Whether they also throw Radeons on high-end desktops is probably not yet determined. (They have a two year roadmap for this rollout, and I think it's pretty obvious they'll start with the portables/iMacs where the benefits of ARM are more likely to outweigh the pain of change for more people.)
Will they have a wide TDP range of designs? Yes. On feasibility, there are two major components to the cost - first is the engineering cost for design. You can bet that these costs are not massive; Apple has roughly $200 billion cash on hand right now. Most of the work will be scaled up as part of their overall design process.
The second cost component is the Non-recurring engineering to get a mask-set made for the chips. A 7nm start right now costs maybe in the range of $20mm? If the Mac Pro is required to stand on its own feet financially, perhaps that will push out timing / push up cost. On the other hand, if one considers the cost of the top end chip to be a marketing cost, it’s literally a rounding error.
GPU - Apple is going to have their own GPUs, and no longer worry about AMD and Nvidia. They’ll have complete control of the hardware and software stack and control their own destiny. I would be very surprised to see dual GPU options.
This isn't just going to replace low-end machines; its every machine they sell, within two years. Probably starting with low-end, but moving up.
That conclusion seems a bit too far fetched from my point of view. There are many users that use Logic on a MBP and with Photoshop it's even more common to use it on a Laptop.
Sooner or later a ARM MacPro is comming but if i'd had to guess i'd say that will take a while. There were 6 years between trashcan and the current cheese grater. So maybe 2025 then ;)
Nintendo Switch uses a nvidia gpu with a very slow and outdated arm processor. Yet, this allows it to run Rocket League, Witcher 3 etc.
Apple, might go with discrete GPU from nvidia/amd to pair it with their arm processors.
1) Before the demo even starts: all Apple apps, pro or casual? Already running. Microsoft Office? Already running. Adobe Creative Cloud? Already running. That's the vast majority of the Mac userbase right there.
2) No apparent hard cuts on the legacy. I was expecting them to not support x86 backwards compatibility if they could get away with it, but apparently they're committed. Even naming the technologies "Universal Binaries 2" "Rosetta 2" is a confident been-there-done-that-will-do-it-again presentation. Unlike last time around, there also doesn't seem to be a major removal of macOS APIs?
3) Acknowledging what kind of x86 stuff machines are used for by showing VMs right away, and (trying to?) show Docker right away. Is that the first Linux demo in an Apple keynote presentation? It was a Linux desktop environment, even.
Now it seems this ARM announcement was a bit rushed by design, flashing by the features without allowing a substantial look. So it's likely we're going to be dissappointed by x86 performance and having to say good bye to APIs (this for sure is the end of OpenGL right? edit: no [1]), but they do leave an impression of having their priorities of broad software support straight and a pretty seamless transition as far as you can get one.
[1]: https://developer.apple.com/documentation/xcode/porting_your...
I do believe they showed a Linux ARM VM. And not a x86 VM.
x86 VM's are probably going to take a massive QEMU performance tax. The positive news it the boost for the Linux ARM space, which will see a massive boost.
Games on Mac? Games on Mac with Windows Bootcamp? Yeah... Maybe buy a console or a second PC...
They're shipping a 'Development Transition Kit' Mac mini with an A12Z this week, so it's not like the numbers are going to stay private for a long time. Even if there's an NDA, someone's bound to break it.
Steve Jobs demoed OSX first. Then surprised everybody by saying, OSX had lived a double life in a secret building for many years (with photo), and that he had been running on an Intel Pentium 4 during the demo all morning. Nothing about performance.
There was also a developer system back then; an Intel Pentium 4 in a PowerMac case.
In a lot of ways, this is far more ambitious, and could mean a lot more for Apple long term, but...
... The one thing that hit me the most was, how impressed I was with Apple back then, and how excited I was that a company could do this. Steve Jobs presented it really well, but this time it felt quite flat.
... I really, wish they worked a bit on their showman-ship. They rushed through so many small things, and the presentation felt unnatural. Like they have all over-rehearsed it, but are still reading while presenting (you could even see eye-movements). It is just too smooth, too generic, and a bit too polished.
Please slow down, focus on only the most interesting bits, and give us time to digest it...
One big question though will be how this devkit benchmarks against the current maxed Intel mac mini. I'm curious if GPU performance beats the current BlackMagic eGPU. (rx 580)
They really don't need to do that much.
It makes sense that they wouldn't:
1. Its dev hardware, not final production hardware. They'll want to compare the A13 or A14 (or whatever SoC they finally use) for benchmarks.
2. Until the apps are optimized, it doesn't make sense for Apple to put itself in the position of bad press with premature figures.
The A12Z is itself only a small update on the A12X from 2018, so it's basically two years behind whatever will ship in actual ARM Macs this fall...
Apple has development kits running in modified Apple TV's. This is a chip that has essentially been out for a few years in iPad Pros. Why would Apple announce numbers based on this? It also assumes Apple will ship future laptops without fans or ports, which is how the development kit is coming out.
Apple will most likely have an A14X out later this year in at least one laptop. That's going to be significantly newer and more advanced than the A12Z in development kits.
The performance and/or battery gains is almost incidental.
It's the CPU in the iPad Pro, performance numbers are out there in the wild. The only big change is the RAM. This isn't a retail product, it's a developer kit. When they release retail Macs I'm sure there will be some performance numbers.
That, however, was not an option. So they have to tread carefully in what they say and they also have to be a bit careful about showing off too much.
They only had to tout the benefits of ARM insofar as to placate the fears of consumers (their Rosetta story plus virtualization story helped there) and to provide some reasonable justification to actually make devs at least a bit excited, even though they have to do additional work.
Plus: No ARM Mac (except the transition kit) currently exists. It’s not even clear if the first Mac they will announce is even finished yet, if only internally. And even if it is finished: Do you think going on stage now and talking about a new MacBook Air that has twice the performance and 50% more battery life as the current MacBook Air – oh, and you can get one in December – would be a good idea?
This is Apple’s tightrope walk to avoid too much of an Osborne effect. I think they are ok with some Osborne effect (if only because they know that even if no one buys an Intel Mac ever again during the next two years transition time they will not go bankrupt, so far from it) but you don’t have to provoke one, right?
I expect plenty of numbers and comparisons when they introduce the actual first ARM Mac.
I guess they did some homework before ditching Intel. The big question Is if they have enough headroom for manufacturing reliable chips with sustained high power.
They are also being very very coy with what they have under their sleeves because of small of an upgrade A13 was over A12.
Same thing happened during the intel transition. The first consumer chips were dual cores, but the DTK was Pentium 4s
That's not this presentation - when they actually ship hardware (transition kit not included) - then they'll talk performance.
I looked all over developer.apple.com and didn't find anything.
For customers, both average users and developers it will be a pain with little to be gained.
The fact that all the demoes were on their top-of-line most-expensive machines fell very weird to me. "Look at this amazing performance" would be great if the demo was on a Macbook Air.
Mobile completely passed it by.
I’ve been seeing more hype about ARM servers for a while with AWS Graviton instances, the new #1 supercomputer in the TOP500, etc.
And of course today we see that Apple plans to transition their Macs to their own ARM chips. Even Microsoft made an ARM-based Windows/Surface product but it didn’t seem to amount to much. I wonder if they’ll want to make another stab at it seeing Apple’s direction with strong vertical integration.
While I don’t think x86 as a platform is going away anytime soon, I feel like its market share and by extension its relevance will slowly dwindle over the next decade or two. Interesting times.
We've been used to x86 dominance on the desktop and servers for so long that I think a future where there are two architectures with critical mass and one of the architectures can be licensed by a number of firms is hard to imagine.
There will be some short term effort and pain but it must surely be a better competitive environment than we have now.
The historic / current Intel and AMD duopoly has surely not been healthy.
The thing we can talk about is Apple's strategic direction. The good version has Apple releasing a notably superior general purpose computer, maybe even gaining more marketshare in the process. The bad version has the Mac turning into an iOS development station. The fact they showed a game of all things does give some encouragement.
Key questions:
1. How open the new OS/Models will be, and how much developer support we get. The more open, the more likely is will be a powerful general purpose computer.
2. Whether Apple can keep riding the tiger regarding processors. I'm sure they did their due diligence, and the new processors will be powerful enough. But x86 isn't dead yet, AMD is capable and even Intel isn't dead - they still have a hand to play.
If Apple can keep at this, developers will flock in and we'll see nice stuff. If x86 (re)gains its momentum, Apple will be left behind, but they will be unlikely to switch back (unifying processors with the iPhone has a lot of advantages for Apple), and we end up with the bad future.
Apple took a chance today, we'll see whether it pays.
I'm curious if Apple's move is going to finally help ARM succeed on the server side.
Apple is gonna knock this out if the park.
I have invested quite a bit into the Mac/Apple ecosystem. A big part of that reason was the longevity of the hardware, along with good resale values.
I hope they do right by their existing Mac customers. As of right now I don't have a strong reason to switch away.
I also hope that Apple does not blow this transition from a quality perspective. Their design choices and attention to detail have left a quite a few things to be desired in the past few generations of hardware.
As for the quality, reply hazy, ask again later? The whole butterfly keyboard of laptops turned out to be a fiasco, and Apple's long-held tendency to push their industrial design right to the edge of thermal and material tolerances got kind of crazy-making in the last few years. Yet so far, I'm really liking my MacBook Air 2020, and the only thing I'd absolutely change about it if I were given a magic wand would be to add a third USB-C port on the right-hand side. I appreciated much of Jony Ive's design work, but I'm hopeful that with him gone, the drive to prioritize minimalism over functionality will be at least toned down.
Well, given that demand for x86 probably won't go away in 3-5 years and that Apple generally makes it impossible to downgrade OSX on new machines, dropping x86 support might actually increase the resale value of existing hardware.
The only way this can work if they implement USB 4. That's earlier than expected but not by much. USB 4 came out last September and everyone was guesstimating 18 months before the first systems ship with it. AMD shipping it with the Ryzen 4xxx laptop chips would've been a really big win but apparently it was too early. And now, as with Thunderbolt, it seems Apple will be the first.
As far as I understand these things, you can connect a TB3 device to a full featured USB 4 port (which Intel plans to market as TB4 just to increase confusion as if there isn't of that around USB C). Not necessarily the other way around: the USB 4 bus while compatible with the TB3 bus, can contain USB packets, TB3 only carried PCIe and DP packets.
Areca has an amazing SAN-in-a-box product: it's a 24 bay 4U RAID box which allows as many as nine TB3 hosts to connect to it at the same time and it's immensely popular with various movie / TV show production. It's less than 10K USD which is an absolute bargain for the capabilities. Consider the 2K price of just one 40gbps Ethernet to TB3 adapter which you'd need for a traditional SAN.
Devices like these make TB3 compatibility an absolute must for Macbooks.
Which is interesting, because the Pro XDR Display can only be driven TB3 [1].
So Apple figured out the licensing for a TB3 controller chip to work in this design (which funny enough would be licensing that IP from Intel), or they are using USB4/TB4, or something else I'm not smart enough to think of.
Now that they're going down the path towards controlling everything in their computer hardware, I can see Apple creating a new proprietary high performance interface to replace TB and use USB for everything else that requires interoperability.
The DTK has two USB-C ports (10 Gbps) and two USB-A Ports (5 Gbps) - so, they definitely have a USB story.
They literally showed a demo of Parallels with Ubuntu for Intel running inside it.
To put it a different way: the initial sales of the ARM-based chips won't be as strong as you think they might be, or as wide spread.
Having both Intel and ARM based systems in the market will even out the sales.
History is repeating itself, it's worth reviewing the previous transitions before making assumptions.
- https://everymac.com/mac-answers/macintel-faq/why-did-apple-...
- https://en.wikipedia.org/wiki/Apple%27s_transition_to_Intel_...
- https://tedium.co/2020/06/16/apple-powerpc-intel-transition-...
Apple released a bunch of PPC Macs after they announced the switch to Intel, so this isn't unprecedented.
They're just trying not to Osbourne themselves too badly. They want you to keep buying Intel Macs, but who's to say how long they'll keep support.
Apple announced the PPC in 1994 and sold new 68K Macs for 3 years at least.
(that probably totally depends on whether Intel actually designs a desktop chip for the first time in nearly two decades, rather than continuing with their current sell server chips as poorly designed desktops path)
They aren’t rushing x64 out the door.
Much like the 2015 Macbook Pro I expect you'll be able sell it for more than you paid for it years later.
No thanks, switching back to Linux. I'm done with this crap.
Maybe, maybe not. Where did you hear that?
I have heard this claim for 10 years now. Still hasn't come true.
Also Apple is committing to a long term pipeline of Intel chips. This makes sense since so many apps will take years to transition. At the same time, they're willing to put their own chips side by side with Intel and they believe people will voluntarily switch. I'm looking forward to the benchmarks.
Intel has been giving developers free libraries for many years which use code specifically optimized for Intel processors. It seems likely that any app that uses one of these libraries will break. Even if Apple's emulator or compiler can work around these optimizations, Intel might release new versions of the libraries that will not work on an ARM processor.
Also, even ordinary changes to MacOS tend to break music apps and plugins. I would expect a change to a new CPU architecture to cause havoc there.
Any app that uses assembly code optimizations that use unique Intel instructions seems likely to break as well. Maybe Apple has perfectly emulated all Intel CPU instructions, but that seems very complex and how often does new complex software work perfectly? Having to buy/upgrade apps to run on ARM may be necessary. And will drivers for USB and thunderbolt peripherals all just work on ARM?
Is this goodbye to choosing your own operating system now? Are the only people Apple cares about web and app developers? Are kernel engineers forgotten about? What about low-level hackers who like to tinker with their hardware or poke around in UEFI?
I'm more worried than excited about this.
> Section 2.2 No Other Permitted Uses
> ... You agree that neither You nor Your Authorized Developers will:
> ...
> (d) display, demonstrate, video, photograph, make any drawings or renderings of, or take any images or measurements of or run any benchmark tests on the Developer Transition Kit (or allow anyone else to do any of the foregoing), unless separately authorized in writing by Apple;
> (e) discuss, publicly write about, or post any reactions to or about the Developer Transition Kit (or Your use of the Developer Transition Kit), whether online, in print, in person, or on social media, unless separately authorized in writing by Apple;
[0]: https://developer.apple.com/terms/universal-app-quick-start-...
If they came out and said here's an open Mac platform with the ability to run macOS, Windows or Linux , open hardware specs, open source drivers and the ability to install whatever you want wherever you want it, I think most people will back it even though initially it'll be painful from a performance and transition standpoint.
But knowing Apple of the recent past or just be more and more closed, limited and Apple or nothing deal.
On one side, I think this switch is a good thing for the industry, as I always believed that ARM was a better choice and that we should get rid of the legacy at some point.
On the other hand, Apple is again tempted to play in their own garden, with a complete disregard of standards and interoperability. They're doing that with Metal, they will certainly do the same with their custom silicon.
The best fit is for Macbooks I think - low power and being able to run iOS software is pretty nice.
For real heavy lifting (6k or 8k editing in Resolve, with raw video codecs, or heavy duty 3D tasks) I don't think I'll be changing from a desktop with AMD Ryzen and top end Nvidia in the next 2 years. Apple high end GPUs in particular are a question mark.
But Apple will probably get there eventually with their own chips - would not put it past them.
I know the 2016-2020 macs are pretty much terrible for Linux anyway due to hardware issues (audio, keyboard, wifi....) so it's no surprise there - but I fear this shift to "Apple Silicon" effectively kills it.
Maybe one more release until they're merged completely.
That's more than twice as long as the transition from PPC. Sounds like they've not yet figured out how to do high-end. Hopefully, they won't be as quick to drop support on the $6k 2019 Mac Pro as they were on the 2005 Power Mac G5 quad (<4 years from release to unsupported by OS X).
Whether that's good for consumers remains to be seen -- I fear it may lead to Macs whose architecture is locked down in a manner similar to iOS devices. That would be a worrying trend.
It's amazing that in their history of making computers Apple has used the 6502/65816, the 68k series, the PowerPC, and now ARM. And along the way there were backwards compatibility options for all of them (although not many people bought and used the Apple II compatibility cards for the Mac, they were really two separate user bases).
It is kind of satisfying in a way to see the ARM architecture come full circle and back to the 'home computer' segment it started in. I look forward to seeing someone port RISC-OS to a Mac, I'm sure it will happen. :-)
I don’t know what other people consider as the lifetime of a Mac (meaning the number of years they’d use a still-working Mac before deciding to buy a new one), but I do wonder just how long Apple’s promise of “supporting Intel Macs for years to come” will turn out to be. Things are surely a lot different now than they were in 2005, especially with much better hardware (and the full transition to 64 bit everywhere).
The demo of Rosetta 2, however convoluted or staged it may have seemed to some, was quite impressive to me.
For me, running Windows in a VM was the killer Mac app. There's always one or two Windows applications that don't have good Mac equivalents. I spent a good portion of my career as a Windows developer working on Mac with a Windows VM.
"Apple's initial press release indicated the transition would begin by June 2006, and finish by the end of 2007, but it actually proceeded much more quickly. The first generation Intel-based Macintoshes were released in January 2006 with Mac OS X 10.4.4 Tiger, and Steve Jobs announced the last models to switch in August 2006, with the Mac Pro available immediately and with the Intel Xserve available by October 2006.[2] The Xserve servers were available in December 2006.[3]"
https://en.wikipedia.org/wiki/Apple%27s_transition_to_Intel_...
If more software developers now need to target ARM architecture, does that mean that it will be easier to port software to other hardware, such as the Raspberry Pi, or is it not that simple?
It will be interesting if one very big company can keep the whole stack going.. Even ps4/xbox went to the common architecture of x86. It could pay off big in price/performance but its risky..
after waiting for years for anyone to replace x86, with a better design, nobody could (Not even intel).
Top left on the arch slide: audio engine. Other on-chip blocks: camera compute, neural engine, machine learning accelerator.
This is about advancing the state of the art in personal digital assistants. The Mac change is in service of the iPhone.
I'm excited. Digital assisstants have stagnated for a long time, because of internet latency and lack of dedicated silicon (and perhaps privacy concerns). This is the way forward.
- Apple being hostile to developers: app approvals (Hey)
- Apple hardware being hard or impossible to upgrade
- MacOS turning into iOS (don't want)
Apple/ARM = best now, because Apple's vast capital from iPhone success has allowed it to build a world-class CPU engineering team from scratch. Building the end products at the same company gives them integration that can't be matched by other companies.
I’m worried it will bring even more close control by them of what we run and how we run it on those computers, but having lots of custom chips (many of them in one package) for all kinds of things with a unified memory architecture is amazing, a modern AMIGA.
I'm sure anything close to the same performance as the Intel chips will have better battery life, especially since they can put in as fine-grained support for throttling and idling as they want. These should cost them loads less per unit than what Intel's selling them, too. They could cut prices a bit and still have higher margins.
Why would I say that? Because the assumption desktop developers have made for decades is that Wintel/Lintel is the norm, everything else is a side dish. And Macs since their Intel shift have conformed to this, if not in terms of API, then certainly in the core architecture decisions. And that means that you design the software "for x86". If you try to run Linux software on a Chromebook you'll often have a nasty experience with these assumptions making things break. And nobody is paying much attention to Win10 on ARM chips.
But now you have a top-down mandate from Apple, which is in a strong position to direct the desktop platform again, possibly the strongest it's ever had. Everyone who follows Apple knows that they tend to obsolete things quickly; they have played this game before. The move they've made is to usher all the developers, not just the mobile ones, to ARM. And that means throwing out a substantial part of old codebases optimized for many generations of Intel chips. It pressures the Linux junkies to be more cross-platform, which in turn topples over some assumptions around Linux desktops themselves. The major distributions will scramble to support Apple hardware.
And a consequence of the assumptions in Linux changing is that you can start doing some ground-up rethinking too. "We're redoing this part of the codebase, let's change the design." And with Apple support may also come Surface support, Chromebook support - giving all the ARM platforms equal treatment. So it's likely that multiple operating systems will see a generational shift, not just Apple's. A big chain of events that will explode some projects and leave others untouched.
And then at the end of that, we might have RISC-V hardware coming over the horizon.
I thought the Mac was amazing back in the mid-80s. I was very impressed with the ipod touch and ipad. I owned an early unibody macbook pro. I can understand the benefits of the closed platform with everything micro-managed by Apple. But it is suffocating. I am more than willing to give up trivial advantages for relatively open hardware platforms and software.
I guess this also means Catalyst’s life span is pretty short and SwiftUI will becomes the focus?
I wonder what that means. There's more to the chip -- what about the core APIs for UI? Does that mean CocoaTouch and UIKit will run natively on macOS?
Virtualization gives us Linux ARM docker images, which is nice, but not the same as running the same Linux docker images that run on the cloud. (while ARM in the cloud can be an option, it is a whole different topic)
The developers will have to find and develop with the ARM equivalent docker image of their production x86 ones, which will make the local dev and production environment unnecessarily more distant.
The good news is that the Docker ecosystem has a relatively broad ARM architecture support, but still, this will be a significant difference with prod environments.
The PS5 apparently has incredible disk I/O, possible due to RAD's compression technology. A super fast compression codec could make a difference too.
I guess we won't have to imagine long, though, since that's exactly what we'll see with the developer kit. Can't wait to see benchmarks of those.
"Developers can start building apps today and first system ships by year’s end, beginning a two-year transition"
https://www.apple.com/newsroom/2020/06/apple-announces-mac-t...
Think about the iPhone SE and how it is supposed to strengthen Apple bottom line on the long run, its more about the recurrent revenue from services than the one shot from hardware.
For references in no configuration of the current Mac mini can you drive an XDR without the use of an eGPU thanks to the extremely limited integrated intel graphics.
I thought maybe Intel was losing ground to TSMC for cultural reasons – being the best while being based in the US is getting harder and harder. But I'm not sure.
PS All those sleeping bugs from C code that was never tested on weaker memory models...
UPDATE: I don't mean the developer transition kit that has a Mac mini with an A12Z, I mean the first consumer macOS device/macBook
Pretty great for development long term.
Now imagine the iPhone's CPU with double the cores and a giant heatsink + fan. I bet it would double maybe even triple a maxed out MacBook's score.
On the other hand, most software does not utilize ARM's NEON instructions (counterpart to x86 AVX). In my tests [1], H.265 software encoding was 3.5 slower on ARM than on x86 in terms of frames encoded per watt of energy consumed.
[1] https://quanticdev.com/articles/h265-encoding-on-arm-cpus
It’ll require some kind of emulation now to run x86/AMD64 instructions on this architecture if I correctly understand the changes happening.
I’m saddened about that. I liked being able to boot my MacBook pro into Windows for games.
My main machine is a 5K iMac which should last me for a couple more years for web dev.
I would get rid of my non-work 13inch mbp if this was the case.
What scares me though is expanding of walled gardens of apple. Mac used to give back to libre culture at least a little bit and push some valuable standards but with native iPhone apps and this closed architecture I'm afraid it will take away from libre and desktop culture. Whether it's a good thing or a bad thing we'll have to see but I'm staying optimistic.
Will be interesting to see how it plays out in practice.
> Virtualization technology allows users to run Linux.
How does it relate to the switch to ARM?
Did they get finally worried about success of WSL on Windows and aim to compete in that area?
[1] https://www.apple.com/newsroom/2020/06/apple-announces-mac-t...
"What would keep Apple from shipping machines with both ARM and Intel CPUs in them? The ARM CPU would run the OS and decide when to ship jobs over to the Intel CPU. I can’t imagine that the home-grown ARM CPU would add much to the total price of the computer."
Would it ever make sense for apple to do that?
Apple: Here we demonstrate desktop Photoshop running on ARM.
The Verge: Write it down.. write it down!!
:)
What's the best non-Apple notebook these days?
- Can the apps downloaded from a website run.
- Can x64/x86 apps both work
- Can I run Excel 2013/Old windows games on Windows XP on Parallels
Apple has deliberately added 'notarization' to try and control the platform as a bout of a landgrap using the ARM transition as an opportunity.
Intel is losing to AMD's Zen and TSMC process nodes.
I'm curious about the future, especially games, if they want to take on consoles.
PS4 and XboxOne are 7 years old and while the next gen looks really good Apple can refresh the productline much quicker (on the other hand it's a good question if people really would want to buy a new console say every year because Apple sure will be aggressive pushing out new models much more frequently)
Made in China or the USA?
Yes, and then you ‘upgraded’ the OS and gratuitously stopped running older software. My final Mac Pro — yes, I was a buyer of Mac Pro grade hardware — still runs 10.6.8 for that reason.
However Apple comes across as cruel when they make decisions like these, which break software distributability of things like native machine learning code. For example one build system that enables that use case is: https://github.com/jart/cosmopolitan
At best these new POWER or ARM architecture Apple PCs are going to be like a C-class Mercedes. So I'm honestly not that concerned. Having distributable open source executables support them shouldn't be that difficult, it's just that it'd add bloat and require trading away important parts of Von Neumman architecture, such as self-modifying code, in order to be done easily.
If Apple wasn't being goofballs, they would have taken into consideration that the x86_64 patents should expire around this year, so Apple could have just as easily adapted the POWER design of which IBM divested themselves, to support x86, by simply bolting on a code morphing layer like Xed. Since it'd be pretty great to be able to buy an Apple PC that doesn't have MINIX lurking inside the chip, without making tradeoffs that could be most accurately described as breaking open source software to save money.
How many devs actually have the setup in place to use a non mobile device?
I also wonder if the current+last gen iPad Pro that has the new keyboard + trackpad case will gain the ability to run Xcode and native macOS apps in the near future.