![]() ![]() On the face of it, there is some sense to it – after all, most W3C and WHATWG specifications have been written algorithmically (rather than declaratively) for a while now. Update: See responses from Chromium-associated folks below. 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 (and friends) 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. Many argue that browser engine diversity is the backbone of the open Web – assuring not only interoperability and user choice but also a bulwark protecting the Web from centralization. Even though they’re a huge burden to develop and maintain, the world is lucky enough to have three major ones, and they’re all Open Source. Most of the complexity and nuance of the Web is stuffed into browser engines. ![]() What willwould a Chromium-only Web look like?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |