[arp242]

I don't know why there aren't more browsers based on Gecko; especially since there are quite a few people who are not exactly thrilled with the general direction Firefox has been going.

There's PaleMoon, which is a fork, and there's SeaMonkey, although the latest version is based on Firefox 60.8 (May 2018), so I guess that's more of a fork than "using the Gecko engine" too? Also the UI is a bit too 1999-esque even for my tastes.

So I guess it's just hard to re-use Gecko? Using QtWebEngine (or QtWebKit before that) is very easy. No really, it's 20 minutes and you have a basic browser. I built a basic "vim-like" browser in the style of Qutebrowser in a day with PyQt (missing a lot of UI stuff and polish, obviously) and I'm not even very experienced in Qt/PyQt (or GUI programming in general).

[detaro]

Yes, Firefox/Gecko is much more one thing, Mozilla apparently even had some problems with that close integration and baked-in assumptions when building the Android variants.

[arp242]

Splitting this out a bit more seems like it would be a good strategic choice, not just for Mozilla, but for the web in general. There are undoubtedly all sorts of technical challenges involved, but betting on only Firefox is putting all eggs in one basket.

Say what you will about Blink/Google, but the easy with which you can build a browser on top of it has spawned a plethora of browsers, ranging from Edge and Vivaldi, to all sorts of more niche ones like Otter and Qutebrowser, and many more.

Half of Vietnam is using Cốc Cốc. Yandex Browser is fairly popular in Russia, UC Browser is popular in China (or rather was, since it was banned) and some other Asian countries.

There's no reason at least some of these couldn't have been a Gecko-based browser.

[The-Compiler]

Hey, I remember that nickname!

Yeah, for smaller projects with only a handful of people behind them, WebKit (via WebKitGTK) or Chromium (via QtWebEngine, Electron, Chromium Embedded Framework) are pretty much the only choices there are. The only exception maybe being Pale Moon.

For browsers which are based directly on the Chromium codebase without being supported by Google, there are definitely many more resources needed - I don't see a particular reason why those couldn't be based on Firefox either. From what I see in QtWebEngine, keeping up with Chromium isn't exactly easy - IIRC they said they need about a person-month to catch up with a new Chromium release, usually with millions of changed lines.

I was hoping for Servo to fill that embedding usecase gap, but it looks like that's been mostly abandoned by Mozilla nowadays. My only other hope is GeckoView: https://mozilla.github.io/geckoview/ - I know at least the people behind Tridactyl would love to see it ported to x86_64: https://tridactyl.xyz/ideas/#port-geckoview-to-x86_64