Comment on Mozilla lays off 60 people, wants to build AI into Firefox

• KillingTimeItself@lemmy.dbzer0.com ⁨8⁩ ⁨months⁩ ago

  librewolf is a firefox fork, anything thats a fork of firefox/chrome is automatically not counted, because it is inherently bulkier than the original (though maybe more secure)

  Unless it’s pissandshittium of course.

  source

  • laughterlaughter@lemmy.world ⁨8⁩ ⁨months⁩ ago

    anything thats a fork of firefox/chrome is automatically not counted

    Says who?

    because it is inherently bulkier

    How is “being bulkier” relevant at all? But let’s just go down that route and say that a fork does not necessarily end up in a bulkier product. A dev team could decide to fork, then remove unwanted features from the original project; which is what’s happening with Librewolf as far as I know (e.g. no Pocket bs.)

    Finally, let’s remember that both Safari and Chrome have their roots on Konqueror’s KHTML rendering engine. By your metric, we should be saying that they don’t count either; because they’re “(definitely) bulkier forks” of KHTML.

    source

    • KillingTimeItself@lemmy.dbzer0.com ⁨8⁩ ⁨months⁩ ago

      Says who?

      says me, the one who made the original comment.

      How is “being bulkier” relevant at all? But let’s just go down that route and say that a fork does not necessarily end up in a bulkier product. A dev team could decide to fork, then remove unwanted features from the original project; which is what’s happening with Librewolf as far as I know (e.g. no Pocket bs.)

      now you just have a patched together, disjointed, mess of a browser, on top of a second dev team, who now needs to unpatch it together, re patch it together, and then somehow repackage that. It’s just hopeless. It’s like trying to turn a full size pickup into a small lightweight town car. It’s just not going to happen.

      Finally, let’s remember that both Safari and Chrome have their roots on Konqueror’s KHTML rendering engine. By your metric, we should be saying that they don’t count either; because they’re “(definitely) bulkier forks” of KHTML.

      It’s worth noting that when a fork is building on top of something, there is a point where the original roots are no longer present, or no longer significantly present. It’s like saying that android is linux. Which doesnt stop the charts from displaying android separately to linux, or chromeos for that matter. Even if it did i don’t like the browsers because they’re too bulky so it’s not like it influences my opinion anyway lol.

      source

      • laughterlaughter@lemmy.world ⁨8⁩ ⁨months⁩ ago

        says me, the one who made the original comment.

        Then it’s a weak argument without real support.

        now you just have a patched together, disjointed, mess of a browser, on top of a second dev team, who now needs to unpatch it together, re patch it together, and then somehow repackage that. It’s just hopeless. It’s like trying to turn a full size pickup into a small lightweight town car. It’s just not going to happen.

        You are assuming way too much. As if Apple and Google did all this with KHTML. Which lead us to:

        It’s worth noting that when a fork is building on top of something, there is a point where the original roots are no longer present, or no longer significantly present.

        And what’s your point by saying this? What does it matter if the roots “disappear,” if the product is good enough for competition?

        Even if it did i don’t like the browsers because they’re too bulky so it’s not like it influences my opinion anyway lol.

        What bulky browsers don’t you like?

        source

        • -> View More Comments