Re: Wait... huh?
[disengage the cloaking device, it is not hostile captain]
I'm still confused on the definition of "faster". You are comparing different workloads and different platforms. Comparing mobile to laptop. Which is fine, a compute is a compute. Except you then say we cannot take a general compute, because on mobile we don't often do that (we do web page and mobile apps, if I'm on the right page). But then compare it to a laptop made for "pro" and not "pro webpage surfing", but what people expect to be productivity. Thus general compute.
So either we need to say the A11 is not the same as the i9, and we cannot compare clocks or workloads. As my casio watch could overclock to 10GHz and be faster than both! XD
Or we say which type of compute, memory etc, and say it's "faster". I'm happy for that, to define it faster in prime, pi, content delivery, encoding or even just latency of a webpage lookup.
But just saying "the A11 [at 2.5GHz] is faster than an i9 [at 2.5GHz]" fails totally to pass logical syntax. As you say though, it is faster for some "type of integer code". That is always a "sometimes", never "it *is* faster". Thanks for the info though!