I’m fine w/ new features being implemented as long as all browser devs agree on doing it the same way!
-
-
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
completely agree, if we stop to fix ALL bugs, we won't be implementing anything new for years
@SaraSoueidan@ppk@jensimmons2 replies 0 retweets 0 likes -
Replying to @gregwhitworth @slightlylate and
I continue to think a pause would be a good thing. Not years, but maybe 6-12 months?
2 replies 0 retweets 1 like -
Replying to @ppk
: you literally do not understand what you're asking for. /cc
@gregwhitworth@SaraSoueidan@jensimmons3 replies 0 retweets 4 likes -
Replying to @slightlylate
for example, Chrome has 48K open bugs according to CRBug
@ppk@SaraSoueidan@jensimmons2 replies 0 retweets 0 likes -
Replying to @gregwhitworth
: and it's going *down*. That triage happens because we have enough engineers. /cc
@SaraSoueidan@jensimmons2 replies 0 retweets 1 like -
Replying to @slightlylate @gregwhitworth and
: what everyone on this thread should hope for is MORE engineers on browser teams.
3 replies 0 retweets 3 likes -
Replying to @slightlylate @gregwhitworth and
not if you've read The Mythical Man Month
1 reply 0 retweets 0 likes
: Browsers are many projects, not one. More headcount == appetite for projects.
/cc @gregwhitworth @ppk @SaraSoueidan @jensimmons
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.