geckoview

I stand by what I said - their code is a convulated mess by design. It's 25 years and they still haven't modularised their code that anyone can use the Gecko engine on the desktop and creating competing browsers. All anyone can do is create a clone of Firefox, which ofcourse, cannot really compete with Firefox or other desktop browser as it will still have all the flaws of Firefox. And this is what Mozilla wants. They may have started with altruistic reasons, but after tasting Google's money, their greed corrupted them. Mobile is a good example. Mozilla realised it was in a precarious position on the mobile platform, which is dominated by Chrome, Opera and Safari. And so they have now been forced to release the Gecko rendering engine for mobile ( https://github.com/mozilla/geckoview ) and are encouraging others to create mobile browsers,

I assume they meant XULRunner[0], which was Mozilla's spiritual predecessor to Electron. Some abandoned modern alternatives included Chromeless[1], Positron[2][3] and qbrt[4][5]. While technically possible using Firefox's XULRunner functionality (`firefox --app app.ini` — mostly undocumented, potentially unsupported in the future), as far as I can tell, Mozilla has abandoned the Electron approach for XUL/Gecko bundling, which is a shame since Firefox itself is basically just an implementation on top of the Gecko XUL runtime. > "[Firefox] is distributed as the combination of a Gecko XUL runtime — libxul, other shared libraries, and non-browser-specific resources like those in toolkit/ — plus a Firefox XUL application — mostly just the files in Contents/Resources/browser/, plus the 'firefox' stub executable that loads Gecko and points it at

Servo is an experimental browser project to explore ideas/techniques: it's never been intended to be a replacement for/embedded into Firefox. What was planned and is happening is that a lot of the exploratory work happening on Servo is being integrated into Firefox in parallel. WebRender is one example of this work: it's (effectively) a Servo component that is now in Firefox. Another example of the above is Stylo/QuantumCSS, Servo's CSS component. This post on Stylo/QuantumCSS gives a good early insight into the overall project to bring these components to Firefox https://hacks.mozilla.org/2017/08/inside-a-super-fast-css-en... > many are jumping to Chromium instead of Gecko. What's the plan there? Is Chromium better/easier to embed? Will I be able to embed Servo at some point? - Chromium is much easier to embed than Gecko - Servo can be e

Disclaimer: Work for Mozilla but not on the browser core, thoughts are my own, grain of salt, etc. My understanding is that on Desktop it's much more difficult than it ideally should be. With that said we've got a pretty solid story being worked on for mobile via GeckoView [1] and Android Components [2], there's a post on the Mozilla Hacks blog about our use of them in Focus [3] and they're also what is being used for building the "next generation" version of Firefox for Android currently code-named Fenix [4][5]. I wouldn't be surprised if there was an effort to get some of the GeckoView work back onto our desktop platforms. [1] https://github.com/mozilla/geckoview [2] https://github.com/mozilla-mobile/android-components [3] https://hacks.mozilla.org/2018/09/focus-with-geckoview/ [4] https://github.com/mozilla-mobile/fenix [5] https://pla