• kava@lemmy.worldEnglish
    11·
    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.worldEnglish
      11·
      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

      • kava@lemmy.worldEnglish
        1·
        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