• kava@lemmy.world
    link
    fedilink
    English
    arrow-up
    22
    arrow-down
    4
    ·
    1 year ago

    I don’t like it because it’s a chrome derivative. Sure, they use Chromium and can edit some things. But at the end of the day, they use the Chrome javascript engine and render the HTML/CSS however Google wants to. Therefore Google more or less defines how that browser represents the web. If Google wants to implement or not implement some web standard, Brave has to follow along whether they like it or not.

    I want less power in Google’a hands, not more.

    • nitefox@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      arrow-down
      1
      ·
      1 year ago

      The chrome javascript engine? V8 you mean? That’s used in Node, it basically powers most, if not all, of the modern web lol

        • nitefox@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Hence the modern. Most modern websites nowadays don’t use php anymore, at least for their FE

          • iopq@lemmy.world
            link
            fedilink
            English
            arrow-up
            2
            ·
            1 year ago

            Laravel is modern enough. If you’re talking bleeding edge web dev, that’s actually on elixir with Phoenix

            Not sure how you count how “modern” something is considering PHP still has new versions and cut lots of releases

      • kava@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        1 year ago

        Good point, I had forgotten node uses v8. It’s powering servers that run node, sure. Not every website uses node. Lemmy I think is rust backend and kbin uses PHP.

        But I mean browser specific rendering. They all follow ECMAScript standard but there are things outside of it. In the past __proto__, a way to get an object’s prototype, only worked in Spidermonkey. Or how the ECMAScript doesn’t specific what order the elements in a for…in loop shows up. Today these are little minor things

        They aren’t particularly important right now (besides hunting weird bugs) because Google follows the standards more or less. But give Google 100% control and you will start seeing dark patterns slip into the javascript itself

        • nitefox@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          The FE can, and probably, still uses node

          Anyway I agree with the sentiment, I use Firefox myself (actually at work I test just against Firefox lol)