What will a Chromium-only Web look like?

#104 · 🔥 267 · 💬 344 · one year ago · www.mnot.net · dochtman · 📷
So my ears perked up when I recently heard from a well-placed contact that "Many in the Chromium community are arguing for a Chromium-only Web." While the Chrome team have long railed against what they perceive as other browsers' plodding implementation of cutting-edge extensions to the Web, it's a pretty big leap to advocate for a Web with only one browser engine. The code is what determines what browsers are capable of and therefore it defines the shape of the Web. In one future Chromium-only world, governance of the Web shifts completely away from Open Standards, and the Web becomes more like Linux - something based upon some historical standards but whose present and future are firmly governed by Open Source practices. A slightly different future would be one where Chromium still draws on the Web standards process for broad review and community participation, but because of the increase in their power, the implementers are effectively in charge, and the SDOs are just along for the ride. DRM. How will the Web look when they're all regulated by multiple governments, or by groups of them? Arguably, wrenching HTML, the DOM, and other core Web infrastructure away from the W3C into the WHATWG - a very Open Source-flavoured club of browser engine vendors - was a first half-step towards this, and that didn't result in any visible negative consequences. Personally, my takeaway is that even in a multi-engine world, we need broader input and accountability than just a bunch of browser vendors agreeing on what the Web should be.
What will a Chromium-only Web look like?



Send Feedback | WebAssembly Version (beta)