7 ms·

There's ungoogled chromium for that. Also doing that doesn't solve the standards problem we currently have. Google is able to push through any "standard". And

by devsda 2y ago

There's ungoogled chromium for that. Also doing that doesn't solve the standards problem we currently have. Google is able to push through any "standard". And those standards "unwittingly" help them maintain their search/ad dominance or prevent competitors. For example see manifest v3 or FloC (a.k.a Topics API). Once they gain enough traction and become indispensible, you either implement them or risk losing users.

hanniabu 2y ago
But why would this change with a new browser written from scratch?
- 38 2y ago
  are you being intentionally ignorant? the more browsers in popular use, the less control each has. currently Chrome has more usage than the other browsers combined: https://gs.statcounter.com/browser-market-share https://gs.statcounter.com/browser-market-share which means Google has significant control over web standards
  - hanniabu 2y ago
    A chromium fork is not chrome. Why assume a fork has to accept upsteam changes?
    - 38 2y ago
      why fork chrome rather than another browser, or starting from scratch?
      - phil294 2y ago
        Because it's infinitely less work than starting from scratch. It's a valid argument.
        38 2y ago
        infinitely doesn't mean what you think it means
      - hanniabu 2y ago
        Less work, more features, proven, security lindy
        38 2y ago
        good point about the lindy
    - devsda 2y ago
      They don't have to. But we have seen how Google can play this game of open core & official versions with AOSP and blessed Android versions with playstore. There will be two classes of products one officially sanctioned version and the others that are used by enthusiasts. Apps or sites in this case may chose to work on one and not on others. Imagine the new wave of "works best on IE" with "best viewed on chrome variations a,b,c". Its not farfetched as some sites already do this. As much as it is easy to maintain a fork, it is that much easy to give up or change path and accept upstream changes.

by devsda 2y ago

hanniabu 2y ago

But why would this change with a new browser written from scratch?

38 2y ago
are you being intentionally ignorant? the more browsers in popular use, the less control each has. currently Chrome has more usage than the other browsers combined: https://gs.statcounter.com/browser-market-share https://gs.statcounter.com/browser-market-share which means Google has significant control over web standards
- hanniabu 2y ago
  A chromium fork is not chrome. Why assume a fork has to accept upsteam changes?
  - 38 2y ago
    why fork chrome rather than another browser, or starting from scratch?
    - phil294 2y ago
      Because it's infinitely less work than starting from scratch. It's a valid argument.
      - 38 2y ago
        infinitely doesn't mean what you think it means
    - hanniabu 2y ago
      Less work, more features, proven, security lindy
      - 38 2y ago
        good point about the lindy
  - devsda 2y ago
    They don't have to. But we have seen how Google can play this game of open core & official versions with AOSP and blessed Android versions with playstore. There will be two classes of products one officially sanctioned version and the others that are used by enthusiasts. Apps or sites in this case may chose to work on one and not on others. Imagine the new wave of "works best on IE" with "best viewed on chrome variations a,b,c". Its not farfetched as some sites already do this. As much as it is easy to maintain a fork, it is that much easy to give up or change path and accept upstream changes.