Who is pushing back against that and how do we get their head on a stick, err, convince them I mean?https://twitter.com/slightlylate/status/913770108245430272 …
-
-
Replying to @robinberjon
Not going to name names, but the form is: 1.) would "break" workflows 2.) everyone will disable, so meh 3.) which throttling profile?
2 replies 0 retweets 1 like -
Replying to @slightlylate
Only point 2 has any substance, and I think it can be addressed with labelling. Eg. call the default, throttling version "Realistic".
1 reply 0 retweets 0 likes -
Replying to @robinberjon
Point 2 *might* have substance, but it's a marginal argument and one that can be answered with data.
1 reply 0 retweets 1 like -
Replying to @slightlylate @robinberjon
And we have a LOT of control over the devtools UI. We can make it really, really hard to disable.
2 replies 0 retweets 1 like -
Replying to @slightlylate
If you make it hard, people will disable once and never re-enable. On the contrary, a "Realistic/Unrealistic" toggles right there would do.
1 reply 0 retweets 2 likes
Again, I want to let clever PMs and UX researchers figure out the right "nudge" there. But the current situation is a massive failure.
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.