DEV Community

Discussion on: Chromium and the browser monoculture problem

johncip profile image
jmc • Edited on

everyone else stopped maintaining separate codebases, duplicating a ton of effort

It's not a duplication of effort, though.

It would be if the standards were always agreed upon in advance, and all the browser vendors did was write code. But that isn't how it works -- the vendors themselves are the loudest voice determining what goes into those standards, which are often based on existing implementations. More voices means more innovation, and more checks against poor choices.

one of the biggest frustrations of my life right now is that Chromium hasn't prioritized Subgrid yet

Honestly, I can't think of an area where we're more spoiled for choice than page layout.

More generally: the web is comprised of many of technologies, the design of which have have various implications for implementers, content creators, and end users -- of those, ease of styling might just be the least important.

Even if one's attitude is "whatever it takes to make the trains run on time," a trinket like CSS subgrids still doesn't strike me as a fair trade for monopoly control of the world's most important publishing platform.

a common browser engine controlled by an independent nonprofit foundation, like the Python Software Foundation, including (though not primarily made of) a few representatives from each participating browser vendor

Sounds neat, but who's going to pay for it? And who decides what they build?