zlacker

>>pabs3+(OP)
I hate to say it, but if you used Chrome to read this, then you're part of the problem.

Awful stuff like this wouldn't stand a chance if Google didn't have such a near-monopoly position.

For the sake of the open internet, please switch to a different browser. IMO, Firefox is best*, but even something chromium based is probably fine. Just not Google Chrome.

* On desktop - Firefox is a bit weaker on Android, with an extemely limited set of extensions (but still better than Chrome with no extensions) and just a Safari wrapper on iOS, with no extensions. (But sync works everywhere!)

(I posted something similar in a different thread recently but I think it bears repeating.)

>>nfried+E7
Web standards are a part of the problem that few people think about. Existing rendering engines grew along with the standards. However, the standards (especially CSS) have become so absurdly complex that implementing a new engine would be nearly impossible. Even Microsoft caved, and Edge is now essentially Chrome.

Some will point out that Chrome is based on open-source software. In reality, however, Google has a huge amount of power here. If Google is serious about this initiative, they will try to force it into the projects, and make it an essential part of the web experience. As others have pointed out, Google is also a primary supporter of Firefox, so they have influence there as well.

>>bradle+zb
THIS...except "a part of the problem" is miserably understated.

Extreme technological complexity is just about the best possible moat a huge business can have. Though in this case "walls around the prison in which the users are incarcerated" might be a better analogy.

And all the prisoners, who just can't resist the endless shiny new goodies added to the web standards, are forever building their own prison walls higher...