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
    link
    fedilink
    arrow-up
    68
    ·
    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
      link
      fedilink
      arrow-up
      15
      ·
      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
    link
    fedilink
    arrow-up
    46
    ·
    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.

    • foo@withachanceof.com
      link
      fedilink
      arrow-up
      8
      ·
      1 year ago

      I don’t know if I’d say separating Gecko from Firefox is all that difficult. About a decade ago I worked on a project at the tail end of my internship at Mozilla to separate Gecko from Firefox Mobile. The idea being to create a sort of GeckoView Android component that could be used like a WebView component to give devs the option to embed Gecko in their app rather than (at the time) WebKit and for Firefox Mobile to become a UI wrapper around a GeckoView component as well. I only had a few weeks to work on it and in that time I had a rough proof of concept running which was an independent Android app that ran Gecko through this new GeckoView component and had a super basic UI to control it. Unfortunately being an internship project I didn’t have time to take it through to completion and being the Firefox OS days at the time the team had other priorities so I don’t believe it ever got fully finished. But point being is that it’s not terribly difficult to separate the two; I did it as an intern in a few weeks a decade ago.

    • Zyratoxx@lemm.eeOP
      link
      fedilink
      arrow-up
      6
      ·
      1 year ago

      Ah, so it isn’t really built do be adapted by others the way Chromium is. Well that’s too bad. At least there’s Floorp although I don’t really have the knowledge to actually check whether their code is fine or not (as they are quite unknown yet) so I’m not so sure whether to trust them.

      Anyways, thanks for your answer! :D

  • 👁️👄👁️@lemm.ee
    link
    fedilink
    English
    arrow-up
    42
    arrow-down
    1
    ·
    1 year ago

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

  • red@feddit.de
    link
    fedilink
    arrow-up
    16
    ·
    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.

  • ratman150@sh.itjust.works
    link
    fedilink
    arrow-up
    15
    arrow-down
    1
    ·
    1 year ago

    Once upon a time internet explorer dominated the web. The web bowed and catered to the jank that was internet explorer…at least until other browsers gained traction. To this day there are some websites that are only designed with internet explorer in mind.

    • VonReposti@feddit.dk
      link
      fedilink
      arrow-up
      17
      ·
      1 year ago

      We can go further. Just recently I saw a website that supposedly “is best viewed full screen, 800x600 or better, in Netscape”

    • danielton@lemmy.world
      link
      fedilink
      arrow-up
      3
      ·
      1 year ago

      And I am convinced people didn’t think the same would happen when everything other than Firefox and Safari switched to being based on Chromium because “nah, it’s open-source, that won’t happen.”

      Well, here we are. The only thing keeping Chrome from completely dominating is that iOS currently requires all browsers to use WebKit, but once there is a real Chrome on iOS, you know every site is going to tell iPhone and iPad users to “lol just download Chrome.”

      This is not the situation I was hoping for, but I saw this coming years ago.

    • sunbeam60@lemmy.one
      link
      fedilink
      arrow-up
      1
      arrow-down
      1
      ·
      edit-2
      1 year ago

      It’s now been replaced by “no message, but sort of only works with Chromium”. As a full-time Firefox user I unfortunately see an increasing trend of “not working right with FF”

  • zerbey@lemmy.world
    link
    fedilink
    English
    arrow-up
    16
    arrow-down
    4
    ·
    edit-2
    1 year ago

    Chrome and its derivatives are by far the most popular browsers, it’s simply easier to go with the most common for maximum compatibility.

    • fsniper@kbin.social
      link
      fedilink
      arrow-up
      11
      ·
      1 year ago

      And that’s the problem. It gives full control power to Google. That’s the reason that popularity needs to be broken.

      • sunbeam60@lemmy.one
        link
        fedilink
        arrow-up
        2
        arrow-down
        1
        ·
        1 year ago

        This is a genuine question, asked by someone willing to learn.

        Why does it give control to Google to use Chromium? It’s open source? Are all the decision makers Google employees? Wouldn’t one assume that forks would occur if a decision was taken as chromium level that was detrimental to, say, Microsoft’s Edge?

        • fsniper@kbin.social
          link
          fedilink
          arrow-up
          4
          ·
          1 year ago

          Google is the maintainer and biggest contributor to chromium.
          https://en.m.wikipedia.org/wiki/Chromium_(web_browser) and they’ve already introduced wei into chromium without any pushback.

          https://kbin.social/m/degoogle@lemmy.ml/t/255346/Google-is-already-pushing-WEI-DRM-Webpage-into-Chromium

          There are forks of chromium already like Vivaldi. You can still use them. Unfortunately using them is not a guarantee that Google can’t use their usage numbers as leverage while politicing or advertising bad behaviour to other parties like social media.

          Worse yet, maintaining a fork is a huge undertaking for a project in the size of chromium. This means in time the fork may struggle to keep up. Or upstream may introduce functions that depends on the bad behaviours and the fork be forced to either adopt both, or adopt none.

    • Zyratoxx@lemm.eeOP
      link
      fedilink
      arrow-up
      10
      ·
      edit-2
      1 year ago

      Seems fair, tho 99,99% of websites are working just fine

      Thank you for your answer :)

    • Zyratoxx@lemm.eeOP
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Fair point. I compared it to Edge because Floorp tries to mimic their UI, it is miles ahead of Edge when it comes to customizability tho. Maybe not as customizable as Vivaldi but it’s very close.

  • sounddrill@lemmy.antemeridiem.xyz
    link
    fedilink
    arrow-up
    4
    ·
    edit-2
    1 year ago

    The jiophones and nokias with kaiOS are based on a fork of gecko, which is a common phone in rural India and goes by different names, sold and made by different companies in different regions all over the world