Apple doesn’t need uop cache while x86 designs do which means more power and area.
ARM has looser memory ordering which improves performance. x86 can do this too, but they have to add an entire memory speculator and all the circuitry to handle when the predictions are wrong. Again, that’s extra area and power.
More controversially, x86 decode is still a significant part of the core area. ARM A715 cut decoder area by 75% just by dropping ARMv7 support (and it’s nowhere near as complex as x86). If the decoder is just 5% of the core area (and basically always on), cutting that by 75% means reducing core size and power by a significant amount. I’d also note that a company doesn’t choose complex 2x4 or 3x3 decoder implementations with massive complexity and inferior worst-case performance unless something is forcing them.
The situation isn’t quite as bad is it might otherwise seem though because 512-bit SIMD as it adds to core size (though arguably doesn’t add very much to most workloads over 128-bit aside from some great new instructions). We can calculate this with Strix Point which uses 256-bit “double pumped” SIMD. The core plus L2 area drops to about 4.2mm2 (or about 3.1mm2 for just the core). Using perfect 1.5x scaling for the core and no scaling for the L2 gives around 3.2mm2. Assuming more reasonable 1.3x scaling (which might still be too generous) gives 3.5mm2 which is still bigger for worse performance on hypothetical N3E vs M5 S-cores.
Even in the best scenario, x86 is way behind in total performance, perf/watt, and area. If we assume the engineers at AMD and Intel are good at their job (a good assumption given how long they’ve been beating everyone else on the planet), it only leaves the ISA holding them back complicating things with legacy bloat.
You’ll see a lot of pushback to this idea, but never much of substance to the assertion.