3 ms·
As far as I can tell, people at Chrome have _very_ strong incentives to propose new standards and ship implementations of them in the browser. Incentives aroun
by bzbarsky 8y ago
As far as I can tell, people at Chrome have _very_ strong incentives to propose new standards and ship implementations of them in the browser. Incentives around then responding to feedback on those standards and getting them into a state where anyone else would implement them are much weaker. Incentives to not ship until this process has happened are nonexistent; in fact lack of interest from anyone else is very explicitly never a reason to not ship something for Chrome, as far as I can tell.
Disclaimer: I work on Firefox, but read the blink-dev list fairly regularly; the last sentence above is repeated pretty often on that list.
- skybrian 8y agoHmm, what do you think of Blink's feature launch process? [1] (I'm no expert, but to me it seems impressively bureaucratic.) [1] https://www.chromium.org/blink/launching-features https://www.chromium.org/blink/launching-features
- bzbarsky 8y agoI think it's a lot better than not having a process, for sure! The hearts of most of the people involved are in the right place, as far as I can tell, and they do listen to feedback some of the time. That said, they feel that if they think something is a good idea then that means they should do it even if others disagree. Which is understandable, of course.