There’s a number of reasons, all of which in concert create the appearance of a performance gap between the two: * Apple has had decades optimizing its software and hardware stacks to the demands of its majority users, whereas Intel and AMD have to optimize for a much broader scope of use cases. * Apple was willing to throw out legacy support on a regular basis. Intel and AMD, by comparison, are still expected to run…
Intel chose and stuck with backcompat as a strategy. They could, tomorrow, split their designs into legacy hardware and modern hardware. They didn’t, but Apple has done breaking generational change many times. Apple also has a particular advantage in owning the os and having the ability to force independent developers to upgrade their software, which make incompatible updates (including perf optimizations) possible.
Ask HN: Why hasn't x86 caught up with Apple M series?
501–510 of 640 posts
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#502Earlier quoted context omitted.
To be honest, I haven't done any research on this, but it's something that crosses my mind from time to time. My laptop has 32 GB of RAM and an i7-14700H processor, with Linux Mint installed. I'm more than happy with its performance, especially considering I bought it for a price that was very cheap for the market. I wonder what specs a MacBook would need to give me similar performance. For example, on Linux with 32…
I don't know for sure, either, but I suspect any recent Macbook with 16GB RAM would be a significant upgrade over 14700H. I don't like macOS, so in recent years, I only use it on laptop (which for me is like, a few on-site meetings per year, plus a few airplane flights). What infuriates me is that my mid-tier Mac laptop for those use cases is now significantly faster than any Linux workstation I can possibly buy... a…
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#503There’s a number of reasons, all of which in concert create the appearance of a performance gap between the two: * Apple has had decades optimizing its software and hardware stacks to the demands of its majority users, whereas Intel and AMD have to optimize for a much broader scope of use cases. * Apple was willing to throw out legacy support on a regular basis. Intel and AMD, by comparison, are still expected to run…
Intel chose and stuck with backcompat as a strategy. They could, tomorrow, split their designs into legacy hardware and modern hardware. They didn’t, but Apple has done breaking generational change many times. Apple also has a particular advantage in owning the os and having the ability to force independent developers to upgrade their software, which make incompatible updates (including perf optimizations) possible.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#504Earlier quoted context omitted.
I thought people stopped believing this around 2005 when Apple users finally had to admit that PPC was behind x86. Even though this was the case for the most part during the entire history of PPC Macs (I owned two during these years) https://chipsandcheese.com/p/arm-or-x86-isa-doesnt-matter
Cheese and Chips makes some bad arguments in that article. Their claim that ARM decoders are just as complex wasn't true then and is even less true now. ARM reduced decoder size 75% from A710 to A715 by dropping legacy 32-bit stuff. Considering that x86 is way more complex than 32-bit ARM, the difference between an x86 and ARM decoder implementation is absolutely massive. They abuse the decoder power paper (and that…
And don’t forget that Apple can do things like completely remove all of the hardware that supports 32 bit code and tell developers to just deal with it.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#505Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#506[dead]
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#507Well, there is a major architectural reason why the entire M-series appears to be "so fast" and that is the unified memory, which completely eliminates the buffer-to-buffer data copying that is probably over half of what a non-unified memory architecture chip is doing at any given time. M-series chips have an architecture that completely eliminates data copying, just reference the data where it is, and you're done.
Apple made a big deal about this, but other iGPUs have done this for years.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#508Earlier quoted context omitted.
I once saw a high resolution CPU graph of a video playing in Safari. It was completely dead except for a blip every 1/30th of a second. Incredible discipline. The Chrome graph in comparison was a mess.
Safari team explicitly targets perf as a target. I just wish they weren't so bad about extensions and adblock and I'd use it as my daily driver. But those paper cuts make me go back to chromium browsers all the time.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#509Earlier quoted context omitted.
Outsourced to who? The only companies with the engineers you’d need are the other CPU makers like Intel, AMD, Qualcomm, and Nvidia. And none of them make a CPU as efficient as Apple does.
cpu yes, but what about the rest of the iphone?
CPU, GPU, neural processor, image signal processor, U1 chip for device tracking, Secure Enclave for biometrics, a 5G modem (only used in the 16e so far)…
They don’t manufacture the chips in house of course. They contract that out to TSMC and other companies.