What is the launch process for a new feature from someone else, when do you provide feedback to other vendors on their proposals?
-
-
Replying to @masinter @Rich_Harris and
"From someone else" == "for features proposed/implemented first in other engines"? Or do you mean "from contributors other than Google within the Chromium project"?
1 reply 0 retweets 0 likes -
Replying to @slightlylate @masinter and
If the question is the first, we try to engage when asked about proposals in important areas. Relatively few of these from other vendors are done via a similar incubation processes (which is a point of contention), so we'll usually get a whiff of them at WG's...which is a problem
2 replies 0 retweets 1 like -
Replying to @slightlylate @masinter and
In those cases, we'd hope other engine projects would send their proposals to similar review (e.g., via the TAG). But they don't
A part of the disconnect is that we're more interested in developer feedback and sentiment than formal WG approval. WG's aren't fitness functions.1 reply 0 retweets 1 like -
Replying to @slightlylate @masinter and
Some WG's exhibit a really weird survivorship bias: they were themselves formed from successful features that were initially designed and launched *outside* the formal process, but now expect everyone to do all new work in an environment they didn't start in...which is


1 reply 0 retweets 0 likes -
Replying to @slightlylate @masinter and
On feedback from other's proposals, Mozilla's positions repo is an interesting way of handling this sort of review flow. We have thought about something similar. Frustrating that Chromium is so far ahead on features that we tend to be the ones pushing most new work = (
1 reply 0 retweets 0 likes -
Replying to @slightlylate @Rich_Harris and
What I'm trying to question is why having the most new features means you're the farthest ahead. When the web platform was new and not very expressive, maybe, but these days shouldn't development processes focus on security, privacy, performance, consistency over features?
2 replies 0 retweets 1 like -
Replying to @masinter @slightlylate and
Larry pretty much summed up Mozilla’s position on the matter (and it sounds a lot like what I hear from Apple folks too). I think we are only working on a tiny handful of new APIs, while investing big on privacy, security, perf, etc.
2 replies 0 retweets 3 likes -
We're investing heavily in those things too. These are not exclusive. It's an abominable strawman to suggest they are.
1 reply 0 retweets 1 like -
Replying to @slightlylate @masinter and
Respectfully, I didn’t suggest that they were. It’s totally a business decision on what things Mozilla focuses on. We are gambling on the things above and less on new APIs.
1 reply 0 retweets 2 likes
The implication is that the web doesn't need those new APIs in order to compete. I'm frankly shocked to hear that, given what we see in usage data and hear from partners. Maybe Mozilla talks to a wholly disjoint set of developers?
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.