• Marc 🐷🌏@veganism.social
      41·
      1 month ago

      @Nalivai
      No not for me, and you know that.

      You’re arguing that you mustn’t rely on another one’s rendering engine, so you’re basically saying that they must build a new one themselves. Right?

      But that goes against your argument that you can’t maintain a rendering engine, because that’s too much work.

      So again. What would *you* (not me) do if you were in control of building a browser? What’s your advice.

      • Nalivai@lemmy.world
        1·
        1 month ago

        I’m saying, both basically and extensively, that if you’re using Chromium as your engine, you don’t get to then turn around and tell that your product is a solution to a corporate world and you’re the alternative of evil Google, or whatever the basic spiel of all this endless ad posts here.
        Building an engine is complicated, forking and continuing Google product is more complicated, I get it. Chromium-based products can be good, and I bet most of them are better than Chrome (but then again, hitting your pinky toe at night when you go to pee is also better than Chrome, so low bar). But “the alternative to Google tyranny” they aren’t. You need to at least fork the engine, support it independently, and substantially alter it, even to be considered one.
        So again. My solution as a browser builder is to ask “how much money I have, and how much people I employ”, and additionally, what’s my actual point of doing it, what am I trying to achieve.