I’ve been thinking a lot about getting something from Framework, as I like their ethos around relatability. However, I currently have an M1 Pro which works just fine, so I’ve been kicking the can down the road while worrying that it just won’t be up to par in terms of what I’m used to from Apple. Not just the processor, but everything. Even in the Intel Mac days, I ended up buying a Asus Zephyrus G14, which had nothi…
Most manufacturers just don't give a shit. Had the exact same experience with a well-reviewed Acer laptop a while back, ended up getting rid of it a few months in because of constant annoyances, replaced with a MacBook Air that lasted for many years. A few years back, I got one of the popular Asus NUCs that came without networking drivers installed. I'm guessing those were on the CD that came with it, but not particu…
Ask HN: Why hasn't x86 caught up with Apple M series?
301–310 of 640 posts
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#302Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#303First, Apple did an excellent job optimizing their software stack for their hardware. This is something that few companies have the ability to do as they target a wide array of hardware. This is even more impressive given the scale of Apple's hardware. The same kernel runs on a Watch and a Mac Studio. Second, the x86 platform has a lot of legacy, and each operation on x86 is translated from an x86 instruction into RI…
This seems mostly misinformed. 1) Apple Silicon outperforms all laptop CPUs in the same power envelope on 1T on industry-standard tests: it's not predominantly due to "optimizing their software stack". SPECint, SPECfp, Geekbench, Cinebench, etc. all show major improvements. 2) x86 also heavily relies on micro-ops to greatly improve performance. This is not a "penalty" in any sense. 3) x86 is now six-wide, eight-wide,…
2. X86 micro-ops vs ARM decode are not equivalent. X86’s variable length instructions make the whole process far more complicated than it is on something like ARM. This is a penalty due to legacy design.
3. The OP was talking about M1. AFAIK, M4 is now 10-wide, and most x86 is 6-wide (Ryzen 5 does some weird stuff). X86 was 4-wide at the time of M1’s introduction.
4. M1 has over 600 reorder buffer registers… it’s significantly larger than competitors.
5. Close relative to x86 competitors.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#304I have the same experience here with my MacBook Air M1 from 2020 with 16GB RAM and 512GB SSD. After three years, I upgraded to a MacBook Pro with M3 Pro, 36GB of RAM, and 2TB of storage. I use this as my main machine with 2 displays attached via a TB4 dock. I'm working in IT and I get all new machines for our company over my desk to check them, and I observed the exact same points as the OP. The new machines are eith…
With Nvidia Now I can even play games on it, though I wouldn't recommend it for any serious gamers.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#305Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#306Battery efficiency comes from a million little optimizations in the technology stack, most of which comes down to using the CPU as little as possible. As such the instruction set architecture and process node aren't usually that important when it comes to your battery life. If you fully load the CPU and calculate how much energy a AI340 needs to perform a fixed workload and compare that to a M1 you'll probably find s…
Like, would I prefer an older-style Macbook overall, with an integrated card reader, HDMI port, ethernet jack, all that? Yeah, sure. But to get that now I have to go to a PC laptop and there's so many compromises there. The battery life isn't even in the same zip code as a Mac, they're much heavier, the chips run hot even just doing web browsing let alone any actual work, and they CREAK. Like my god I don't remember the last time I had a Windows laptop open and it wasn't making all manner of creaks and groans and squeaks.
The last one would be solved I guess if you went for something super high end, or at least I hope it would be, but I dunno if I'm dropping $3k+ either way I'd just as soon stay with the Macbook.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#307Battery efficiency comes from a million little optimizations in the technology stack, most of which comes down to using the CPU as little as possible. As such the instruction set architecture and process node aren't usually that important when it comes to your battery life. If you fully load the CPU and calculate how much energy a AI340 needs to perform a fixed workload and compare that to a M1 you'll probably find s…
> All that to say: M1 is pretty fast, but the reason the battery life is better has to do with everything other than the CPU cores. That's what AMD and Intel are missing. A good demonstration is the Android kernel. By far the biggest difference between it and the stock Linux kernel is power management. Many subsystems down to the process scheduler are modified and tuned to improve battery life.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#308Earlier 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.
Arm exists, it is unknown how much tech apple gets from Arm.
Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#309Re: Ask HN: Why hasn't x86 caught up with Apple M series?
#310Earlier quoted context omitted.
This argument never passes the sniff test. You can run Linux on a MacBook Pro and get similar power efficiency. Or run third party apps on macOS and similarly get good efficiency.
unfortunately, contrarily to popular belief, you cannot run Linux natively on recent macbooks (m4) today.