• nyakojiru@lemmy.dbzer0.com
    link
    fedilink
    English
    arrow-up
    5
    ·
    11 months ago

    Horrific but strategically inevitable, switch to chromium engine, and do your own privacy related fork . Like all the other browsers.

    • Samuel C@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      ·
      11 months ago

      fork

      what if google chrome decided to close the fork by changing the license to something restructive, i mean the fork can goes on for a little while but we are still depending on the resources of a Big $$ corporation…

      firefox is the only way for a free web…

      • jcg@halubilo.social
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        11 months ago

        Then they’d be alienating the open source community that makes a lot of contributions (though much of chromium is still essentially built internally). They also wouldn’t be able to lock down the code that’s already been released under the more permissive BSD license.

        Now, a fork of Chromium is its own beast. Some searching shows that just to build it takes 30 minutes on a decent workstation. It’s huge, which makes me think it’s the kind of project that could only really be maintained by a large company. Not necessarily a Google sized company, but a large one nonetheless if you seriously want to remove the dependency on Google.

        EDIT: turns out it’s Chrome that takes that long to build, which includes things not in Chromium like Widevine, licensed codecs, telemetry, sync, that kind of thing.