@wycats: because developer interest in things you can't send a link around to is low.
-
-
Replying to @slightlylate
@wycats: canary/dev might as well ask users to flip flags, which they could already do for many of these things1 reply 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate but you're stuck on fairly old and buggy versions of the feature, when Canary is full of bugfixes.1 reply 0 retweets 0 likes -
Replying to @wycats
@slightlylate I think I can see the motivation, but it feels fairly narrow: stalled "Stage 0" / "Early Stage 1" in TC39 parlance?2 replies 0 retweets 0 likes -
Replying to @slightlylate
@slightlylate seems legit. my main concern is that if the feature is actively developed, the time lag btw canary->stable is large.1 reply 0 retweets 0 likes -
Replying to @wycats
@slightlylate so for such features, you'll be using old, buggy, already-fixed, already-changed features.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats you'd be able to test in canary and see the bug fixes. But end users don't have canary. They run on stable /@slightlylate1 reply 0 retweets 1 like -
Replying to @yoavweiss
@yoavweiss@slightlylate This isn't *really* about end users, due to the caps.1 reply 0 retweets 0 likes -
Replying to @wycats
@wycats IIUC, the experiments must run on end users. Caps are there to avoid reliance on features /@slightlylate1 reply 0 retweets 1 like
@yoavweiss @wycats: the balance is about making a new feature juicy *enough* to be worth investing in an experiment.
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.