3 ms·
> but perhaps such discourse should be private before being finalized as early commenters from Mozilla can have a premature influence on public opinion. No, it
by illiarian 4y ago
> but perhaps such discourse should be private before being finalized as early commenters from Mozilla can have a premature influence on public opinion.
No, it shouldn't. It's a good thing all discussion is happening in the open. See how Firefox devs still have their reservations but Chrome already shipped it to prod completely ignoring any such reservations.
- Yoric 4y agoFWIW, that's a pretty standard behavior for Chrome teams) and, as far as I understand, related to how they are evaluated within Google. More spec proposals == good for your career. Shipping a feature (even if it's non-standard) == good for your career. Ensuring standard-compatibility == noop. Source: I used to be a browser dev annoyed by how Chrome kept shipping non-standard features.
- sam_goody 4y agoThat's a feature, not a bug. As long as Chrome has > 80% market share, the more non-standard features the ship, the more they cement their position. Same as IE6, which was intentionally non-standards. Sites would be designed to work in IE, and would not work on Netscape. Considering how much spying and how much lock-in Chrome provides for Google, anything that makes devs design for Chrome only is a huge advantage.