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

  • The Cuuuuube@beehaw.org
    139·
    11 months 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
      29·
      11 months 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.

    • YMS@kbin.social
      25·
      11 months 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.

      They both are of very similar age actually. The old Netscape rendering engine originated in the early 90s, but Gecko was a rewrite from scratch that was first used in a browser in 1998.
      Blink is based on KHTML which is based on khtmlw, which was written at some point in the mid-90s, but as well saw a complete rewrite in 1999.

    • argv_minus_one@beehaw.org
      7·
      11 months ago

      The only time I ever had memory problems with Firefox was when I tried to run it on a potato. That complaint has always been bullshit.

      Edit to add: The aforementioned incident was in 2010, on a machine with only 512MB of RAM. Like I said, potato. Chrome back then was somewhat more memory-efficient than Firefox, and could support three open tabs on that machine before it started thrashing, whereas Firefox would thrash with just one. Both browsers performed abysmally under such a severe RAM shortage, but Chrome was slightly less abysmal. Slightly. I seriously doubt the current version of either browser would be usable on that machine, although I don’t have it (I gave it away soon after this incident) so I can’t check.

      • monk@lemmy.unboiled.info
        1·
        5 months ago

        Firefox ate my RAM joke is ridiculous. Nokia N900 has 256MB RAM. Fennec for Maemo had electrolysis (multiprocessing) turned on. In version 4. Years before the desktop Firefox. You really need to go old-school embedded for Firefox to eat your RAM.

    • Aatube@kbin.social
      2·
      11 months ago

      Gecko was probably based on early 90s code but it wasn’t out until 2000. It’s still older than almost everything else though.

      • Efwis@lemmy.zipEnglish
        1·
        11 months ago

        Actually ff is the old Netscape navigator which was popular in the early to mid 90’s. When Netscape didn’t take off like they hoped it was retooled a little bit and turned into ff

        • Kangie@lemmy.srcfiles.zip
          7·
          11 months ago

          When Netscape didn’t take off like they hoped it was retooled a little bit and turned into ff

          Don’t you mean “when Microsoft abused their monopoly to crush the competition it was open sourced”?

        • Aatube@kbin.social
          2·
          11 months ago

          Yes. That still doesn’t change how Gecko (which is basically a rewrite of the old Netscape engine) was not released until 2000.

    • Zyratoxx@lemm.eeOP
      2·
      11 months ago

      Ah, yeah, and it’s probably too laborious to change the browser base now.

      Thank you for your answer! :D