I mean, I like Firefox, but I’d love to see Vivaldi based on Firefox/Gecko. There’s Floorp, which is similar in some ways but it’s more like an Edge built on Firefox than Vivaldi.

Edit: Thank y’all for your answers. :D

I want to link !@bdonvr@thelemmy.club 's post because it is a similar quesion. https://thelemmy.club/post/718914

  • red@feddit.de
    3·
    2 years ago

    KHTML/WebKit/Blink has always been built with the intention of many browsers (or anything else that needs a rendering engine) integrating it, thus it’s very easy to do so.

    Gecko hasn’t been built with the intention of being integrated into any browser at all. Gecko isn’t integrated into FF either. You integrate the browser into Gecko, not the other way around. It’s closer to building a browser in Electron than to building a browser with the Blink engine.

  • The Cuuuuube@beehaw.org
    1·
    2 years ago

    Blink has a younger code base that’s easier to build on. Gecko has been around since the early 90s and has some ancient evils lurking deep within. At least that was the reasoning a while ago. As Mozilla has been putting a heavy emphasis on code correctness for the last few years, that may no longer be the case. Then again, momentum is a big deal, and I still see people saying the don’t want to try Firefox because its memory inefficient even though they fixed that bug almost a decade ago now and its less resource hungry and faster than chrome now

    • American_Jesus@lemm.ee
      0·
      2 years ago

      Blink is a fork of WebKit wich is a fork of KHTML, KHTML exist since the '98, the codebase isn’t that younger too. Was tweaked by Apple then by Google, with some features that don’t exist on other engines.

  • trimmerfrost@lemm.ee
    1·
    2 years ago

    Performance, long term assurance. Sorry my brain’s not working RN. That’s all I can think

  • 👁️👄👁️@lemm.eeEnglish
    1·
    2 years ago

    I’d imagine because they want as little compatibility issues with their product as possible so they just copy what’s already popular.

  • hitwright@lemmy.worldEnglish
    1·
    2 years ago

    Gecko was pretty shit performance wise until Firefox quantum in 2017. Back then even Apple decided it’s better to use webkit for it’s browser.

    It’s difficult to say exact reasons for each browser. But for Chrome enjoying the dominant position before that, it was better to jump on Chromium as base just for better compatibility with most websites.

    Tooling followed soon after

    • Aatube@kbin.social
      1·
      2 years ago

      Apple didn’t “decide it’s better to use webkit”, they MADE WebKit (from forking KDE). Back when they started WebKit Gecko was only out for a year and heavily associated with Netscape, while KDE’s was already mature