big.Little simply means you have big, hungry, power cores and smaller, slower efficiency cores that exist in the same CPU. Intel's implementation isn't any different than Apple's. It's just that Intel is pushing both the P cores and E cores harder than Apple.Intel's current strategy is not the "classical" big.little though. Its parallel thoughtput. They are not focusing on combination of high performance cores for burst and high efficiency cores for efficiency, they are focusing on MANY mid-efficiency cores for higher performance in multi-core workloads. Alder Lake already comes with 16 cores (24 threads!), and so requires software that can take really good advantage of multiple cores to use the chip well. Raptor Lake is supposed to up the number throughput cores to 16, that will essentially result in a 32-thread CPU. Great for benchmarks, a bit awkward for real-world performance.
This is very different from, say, Apple's big.little (where high-performance cores use as much power as Intel's efficiency cores, and the efficiency cores are really there for efficiency). And it is also very different from what AMD is rumoured to do (their performance cores are also more efficient than Intel's). And of course, there is the modern Android approach... but the main purpose of their single "very fast core" is essentially benchmarking shenanigans.
If Intel wants, they can simply dial it down and increase efficiency.
Alder Lake is incredibly efficient (for x86) when you don't push it past its limits.
We know nothing about AMD's big.Little plan. That's not happening until Zen5 which might be 2.5-3 years away.
People like to crap on Intel. But they're clearly ahead of AMD right now in non-server market and based on roadmaps, they're likely to stay ahead. Of course Apple is a different story.