Because it represents a generalized view of how slow the CPUs are on Android vs iOS. Don't care so much about browser v browser.
-
-
Replying to @dhh
It's a combination of factors including optimization effort, the gameability of the benchmark, and CPU speed.
1 reply 0 retweets 1 like -
And the next gen pixels come out tomorrow, so probably the worst possible time to evaluate pixel perf.
1 reply 0 retweets 0 likes -
Replying to @wycats
Tested the 835 chip the Pixel 2 will use. Scored 60-65 in the Samsung S8 and OnePlus 5. Still atrocious.
1 reply 0 retweets 0 likes -
Replying to @dhh
Yehuda Katz 🥨 Retweeted DHH
https://twitter.com/dhh/status/846627223176167424 … I guess this is also Android's key insight.
Yehuda Katz 🥨 added,
2 replies 1 retweet 3 likes -
Replying to @wycats
I’m fact, with commodity rendering, poor performance is what requires the bending. Extra time spent on optimizations.
2 replies 0 retweets 1 like -
Replying to @dhh
1: I probably spend as much time as anyone on these optimizations, but I think the details here matter a great deal, and that focusing ...
1 reply 0 retweets 0 likes -
2: on particular microbenchmarks, if it works, is likely to bring us back to the bad old days of wasted optimization effort in an ...
1 reply 1 retweet 1 like -
3/3: embarrassment-driven-development incentive structure. It has taken a lot of effort to get past this, and I don't want to go back.
1 reply 1 retweet 5 likes -
Replying to @wycats
Again, don’t really care much about whether Chrome is 25-50% slower than Safari. I care that iPhone is 4-5x faster than Android.
1 reply 0 retweets 7 likes
What makes you so confident that: 1. This benchmark is representative 2. This benchmark isn't easy to game (so "fixing it" will do no good)
-
-
the onus is kinda on you here
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.