The chances of actually getting a only a single core working on something are slim with multitasking, I had to purpose build stuff - hardware and kernel/etc for CPU mining a half decade ago to eliminate thermal and pre-emption on single threaded miners.
Single thread performance has been stagnant forever because with Firefox/chrome and whatever the new "browser app" hotness is this month your going to be using more than 1 core virtually 100% of the time, so why target that. Smaller die features means less tdp which means less throttling which means faster overall user experience.
I'm glad someone is calling out the M1 performance finally.
Also, I'm not sure what's up with Geekbench results on MacOS, but here's a 5950x in an iMac Pro that trounces all the results we've mentioned here somehow.[1]
MacOS, being unix based, has a decent thread scheduler - unlike windows 10/11, which is based on windows NT and 32bits, and never cared about anything other than single core performance until very very recently.
https://browser.geekbench.com/v5/cpu/compare/10517471?baseli...
They look to be on par to me. Things will be less murky if and when Apple finally scale this thing up to 100+ watt desktop class machines (Mac Pro) and AMD move to the next gen / latest TSMC process.
In my view Intel and AMD have more incentive to regain the performance crown than Apple do at maintaining it. At some point Apple will go back to focusing on others areas in their marketing.
But tbh, it doesn't seem the new hotness in chips is single core CPU, it's about how fancy you spend the die space in custom processors, in which case the M1 will always be tailored to Apple (and presumably Mac users') specific use-cases...