As read from my Mozilla Firefox…

  • Avid Amoeba@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    9 months ago

    The Debian community already maintains a Chromium fork. How much does that cost?

    The human time needed should grow with the number of patches that need to be applied to the upstream code base, because some will fail now and then. This is what I refer to as “fatness” of the fork. The more patches, the fatter. It should be possible to build, packege and publish a fork with zero patches without human intervention, after the initial automation work. Testing is done by the users as it always has been in Debian and its derivatives. You’re referring to a few full-time developers and I simply don’t see the need. Maybe I’m missing something obvious. 😅

      • laurelraven@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        2
        ·
        9 months ago

        Add into that, I’m betting googie will actively try to make downstream forks difficult to maintain without accepting the components they want to force on everyone like manifest v3

          • laurelraven@lemmy.blahaj.zone
            link
            fedilink
            English
            arrow-up
            2
            ·
            9 months ago

            I have no interest in giving them the benefit of any doubt, they not only haven’t earned it but actively squandered and destroyed the trust they had earned in the past.

            They’ll actually have to do something to make themselves trustworthy again, and even if they do, there will always be the threat of them reverting to what they are now or worse looming over every good thing they do.

            They not only became what they set out to oppose, they’ve become so much worse.