4 ms·
That's a pro. Variation sucks. What you want is competing contributors and stakeholders to ensure a single entity's interests don't win. I would argue the massi
by schmichael 11y ago
That's a pro. Variation sucks. What you want is competing contributors and stakeholders to ensure a single entity's interests don't win. I would argue the massive WebKit/Chromium ecosystem has lots of competing contributors.
- pcwalton 11y ago> That's a pro. Variation sucks. No, it doesn't. A browser engine monoculture means that a single engine's bugs and quirks become the standard. As a result the Web platform gets worse, and it becomes harder for new browser engines to enter the market. For example: http://robert.ocallahan.org/2013/02/a-small-example-of-value-of-browser.html http://robert.ocallahan.org/2013/02/a-small-example-of-value... > What you want is competing contributors and stakeholders to ensure a single entity's interests don't win. That is not the case in practice with either WebKit or Blink. > I would argue the massive WebKit/Chromium ecosystem has lots of competing contributors. Not really. There are two primary ones: Apple and Google. Both organizations have essentially as close to absolute sway over their respective projects as to what Web platform features they implement and how they choose to implement them as to make no difference.