this post was submitted on 13 Aug 2023
2636 points (97.8% liked)

Memes

45525 readers
1022 users here now

Rules:

  1. Be civil and nice.
  2. Try not to excessively repost, as a rule of thumb, wait at least 2 months to do it if you have to.

founded 5 years ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 55 points 1 year ago (1 children)

Mozilla doesn't make it as easy to use the Firefox / Gecko engine in other projects, which doesn't help for adoption.

[–] [email protected] 9 points 1 year ago (2 children)

I'm way out of the loop, but is the issue that they actively make it difficult to use the rendering engine or is it that the cost to modularize it isn't worth the payoff to Firefox itself? A subtle but important distinction IMO. I always felt it was the second, but maybe I was being dense?

[–] [email protected] 6 points 1 year ago (1 children)

Back in the days it was possible to use Firefox engine to create apps. It was called XUL. Heck, Firefox itself was just a XUL app! But then they decided it wasn't worth it for whatever reason and now their engine is tightly integrated.

[–] [email protected] 4 points 1 year ago

I believe it might be still possible with UXP - a hard fork made for Pale Moon project.

Pale Moon is based on a derivative of the Gecko rendering engine (Goanna) and builds on a hard fork of the Mozilla code (mozilla-central) called UXP, a XUL-focused application platform that provides the underpinnings of several XUL applications including Pale Moon. This means that the core rendering functions for Pale Moon may differ from Firefox (and other browsers) and websites may display slightly different in this browser.

[–] [email protected] 4 points 1 year ago

They don't try to make it difficult, but they make code changes that make it clear they have no concern for anyone who might be trying to use the engine anywhere other than in a retail build of Firefox, without providing things like deprecation warnings or upgrade paths.