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

  • Jeena@jemmy.jeena.net
    2·
    1 year ago

    The code is already prepared very well to be embedded into something. I remember trying to embed the javascript engine SpiderMonkey into a project (I needed C bindings which I then could use in Erlang). After a week or so trying and extending, etc. we gave up and tried V8 which we had running within one hour with good documentation great APIs and so on.

    I myself have been Firefox user since Firefox came out but trying to embed it myself and failing I kind of get why others choose Chromium/Blink as their base.

    • Zyratoxx@lemm.eeOP
      1·
      1 year ago

      Oh, I see. I had an internship last year where I developed a WebApp and I only got a slight glimpse of the differences between Blink & Gecko but even that already influenced my code so I can kinda imagine the struggle :')

      Thank you for your answer! ^^

  • krdo@lmmy.net
    2·
    1 year ago

    The main reason I’ve heard is that chromium is far easier to embed than Gecko. Gecko isn’t something you embed like a library. It’s something you build upon. Detaching Gecko from Firefox UI (or Thunderbird for that matter) is supposedly really hard.

  • red@feddit.de
    1·
    1 year 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.

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