lol, just mentioned that last week to someone ;)
-
-
Replying to @gregwhitworth @ppk and
we try and balance this, you may notice nothing happening in feature are Y, and it's because we're doing that
1 reply 0 retweets 0 likes -
I’m fine w/ new features being implemented as long as all browser devs agree on doing it the same way!
1 reply 0 retweets 2 likes -
sure that's what standards are for, but like most things it's never that black and white
3 replies 0 retweets 0 likes -
: nor should we expect it to be. Progressoften messy; hence I'm trying to orient by evidence
2 replies 1 retweet 2 likes -
Replying to @slightlylate @gregwhitworth and
: this is why extensibility matters: gives devs power while helping to build case for features
1 reply 0 retweets 1 like -
Dumb question: isn’t it possible that devs also end up messing stuff & causing more inconsistencies tho?
2 replies 0 retweets 0 likes -
Replying to @SaraSoueidan @slightlylate and
I’m specifically referring to Houdini stuff in this case. One dev may do same stuff different way(s)?
1 reply 0 retweets 0 likes -
Replying to @SaraSoueidan @slightlylate and
I may be completely off & misunderstanding this whole thing tho so happy to be corrected!
1 reply 0 retweets 0 likes -
Replying to @SaraSoueidan
: happy to discuss at length. Basic insight is that we get X features per year. That's fixed. /cc
@gregwhitworth@ppk3 replies 0 retweets 1 like
: so question becomes, if we only get X per year, how should we "spend" them? What's most effective?
/cc @gregwhitworth @ppk
-
-
Replying to @slightlylate
: my thesis is that we should spend those features in ways that give us confidence later. /cc
@gregwhitworth@ppk1 reply 0 retweets 0 likes -
Replying to @slightlylate
: for instance, we derived the Web Components deliverables by looking at frameworks & experiments /cc
@gregwhitworth@ppk2 replies 0 retweets 0 likes - 9 more replies
New conversation -
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.