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 !@[email protected] 's post because it is a similar quesion. https://thelemmy.club/post/718914
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.
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.
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
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
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.
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
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.
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.
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.
