Call me when there is something to show besides geekbench synthetic scores (which heavily favor Apple iOS devices, going as far as utilizing asic and specialize

Call me when there is something to show besides geekbench synthetic scores (which heavily favor Apple iOS devices, going as far as utilizing asic and specialized instructions for stuff like compression and javascript) and javascript benchmarks which run for milliseconds and are super prone to highly specific tuning (See the general uselessness of stuff like sunspider for actually measuring anything a user would consider to be performance) from the article: The next issue I want to address are fallacies I've seen permeate discussions around ARM performance: that a benchmark is not at all useful because it is flawed or not objective in some way. I understand the reaction to a degree (I once wrote an article criticising camera benchmarks that reduce complex data into single scalar numbers), but I also believe that it’s possible to understand the shortcomings of a benchmark, not to approach it objectively, and to properly consider what it might indicate, rather than dismissing it out of hand. This is some pretty insipid hand waving, they then go on to address exactly nothing about any shortcomings, and keep pretending that these benchmarks generalize meaningfully.