#Mozilla is no longer in the vanguard of the #openweb. What was once an organization dedicated to #decentralizing #web technology has now gone over to feeding #SaaS chains.

If it was about local and #selfhosted #AI, it'd be another thing - which was their original stance. But in their pursuit of funding they've abandoned the principles that made Mozilla great.

It just keeps getting worse - #Firefox to "evolve into a modern AI #browser" | GamingOnLinux
https://www.gamingonlinux.com/2025/12/it-just-keeps-getting-worse-firefox-to-evolve-into-a-modern-ai-browser/

It just keeps getting worse - Firefox to "evolve into a modern AI browser "

Just like Google plan with Chrome, Mozilla aren't sitting still on expanding Firefox into something resembling a web browser but with more AI.

GamingOnLinux

Maybe #Waterfox, #ZenBrowser, #TORBrowser, #PaleMoon, #IceCat & #LibreWolf should come together and form a new organization to fork and maintain a separate version #Gecko engine.

Perhaps even make a goal to transition from Gecko to the #Servo engine, creating a path for other Gecko based browsers to also follow suit.

There needs to be repercussions. There needs to be blowback. There needs to be culpability.

And no, everyone using Blink is not a good solution - at all.
https://www.waterfox.com/blog/no-ai-here-response-to-mozilla/

No AI* Here - A Response to Mozilla's Next Chapter - Waterfox Blog

Mozilla's pivot to AI first browsing raises fundamental questions about what a browser should be.

Waterfox

@hopland Pale Moon will not follow suit in the goal of replacing Gecko with Servo (which we thought Mozilla would be doing in its destruction of everything from the Netscape legacy it inherited the torch from, but yet didn’t do and instead laid off the Servo team). The exclusion of Rust from our platform codebase is intentional. Having to juggle with many languages in the platform like C/C++ (having to note the subtle difference between the two siblings as well when compiling!), JavaScript, XUL, Python, autoconf… That takes constant effort. Rust with its own quirks and ecosystem would probably make it triple for us.

We’ve also forked Gecko a long time ago into Goanna since 2016 with the release of version 26 of Pale Moon, and an organization that maintains Goanna and the Unified XUL Platform that Pale Moon builds on is also there, albeit less formal than Mozilla’s (more accurate to call MCP a collective rather than a corporation or foundation): https://www.moonchild.productions/

Fun fact, when we were starting up our final hard fork of Mozilla’s platform from ESR 52, which became the Unified XUL Platform aka UXP, we did ask other Mozilla-related projects like SeaMonkey and Waterfox if they’d like to join forces with us. They refused and instead tried to fork from ESR 56 in their own. Waterfox eventually had to abandon it (the “Classic” version has not had any updates since 2022), and SeaMonkey is still stuck trying to fully adapt to current mozilla-central but couldn’t because it currently breaks their internet suite… As of right now SeaMonkey is still struggling with implementing Google WebComponents which breaks a lot of websites for them.

Goanna

The Goanna layout and rendering engine

@job fair enough. Thanks for the info.
@hopland Browser engine variety is always going to be a net positive for users. It prevents control of the browser ecosystem by singular groups with ulterior motives

@OpenSauce I come from the days of developing for IE6. Preaching to the choir. That being said, we got some choices.

* blink (chrome, edge, Vivaldi, electron, etc)
* WebKit (spiritual successor to KHTML, kind of "neglected" by Apple to prevent WPA from harming their App Store ecosystem)
* gecko (firefox, zen, waterfox, etc)
* ladybird (brand new browser engine)
* servo (previous Mozilla project, aiming for embedded, written in Rust)

We've come a long way since Netscape, I'll tell you what