Comment by xp84

> If you want your project to remain the currently dominant web browser, you better keep developing APIs people love, you better keep doing it faster than your competition can keep up with implementing them, and you better keep dominating the web standards committees.

Hey look, an incidental collision with my point!

I'd argue that Google specifically doesn't have nearly the obligation to keep doing these things as long as they are the ones who own Chrome, due to how many other things they can do to put their finger on the scales.

For instance, they could do things like:

- Show overwhelming amounts of ads in everyone's Gmail and say "Switch to Chrome for an ad-light experience."

- Or limit YouTube to 360p in non-Chrome browsers.

- Or only show the sponsored Google Search results (no organic) to non-Chrome browsers (let's be honest though, most non-nerds never click non-sponsored results anyway, and could scarcely find them even in the current Search UI).

- Or limit any new features on Google Workspace to Chrome browsers.

Google can maintain the Chrome near-monopoly using leverage from their other monopolies and near-monopolies. And they can use the Chrome near-monopoly to preserve and expand their marketshare of those other products. A very neat virtuous cycle (for Google). I don't think it promotes the health of free markets or consumer choice.