News for hackers. Stuff that matters.
Re:Update on Firefox Send and Firefox Notes by thesimon on Thursday September 17, 2020 @05:16PM (#24510060)
>and Management division may force in future to ditch Gecko and adopt Webkit/Blink in the hope that it could bring more userbase (just my thought) to lessen maintainance and focus on revenue.

They laid off most people working on Servo, so the adoption of WebKit/Blink seems rather likely.

Re:Update on Firefox Send and Firefox Notes by orclev on Thursday September 17, 2020 @05:21PM (#24510108)
I certainly hope it doesn't come to that. Servo was really starting to show serious improvements in both memory usage and speed relative to Gecko and Webkit. It would be a shame to see Firefox devolve into just another rebranded Webkit browser, particularly since everyone loses when things devolve to a monoculture.
Re:Update on Firefox Send and Firefox Notes by jdashg on Thursday September 17, 2020 @05:45PM (#24510330)
Servo was never actually the heir-apparent to Gecko.
Re:Update on Firefox Send and Firefox Notes by nanagojo on Thursday September 17, 2020 @09:03PM (#24511871)
You sure? https://blog.mozilla.org/blog/2013/04/03/mozilla-and-samsung...

> Servo is an attempt to rebuild the Web browser from the ground up on modern hardware, rethinking old assumptions along the way.

Re:Update on Firefox Send and Firefox Notes by dralley on Thursday September 17, 2020 @09:51PM (#24512145)
1) That was written in 2013

2) It was an attempt to rebuild a browser engine up from the ground up on modern hardware - and large parts of that work landed in Firefox.

I've tracked their progress for quite some time. There was never a concrete plan to replace the DOM handling components of Gecko with the DOM handling components of Servo.

Re:Update on Firefox Send and Firefox Notes by btrask on Friday September 18, 2020 @10:42AM (#24517371)
It was written in 2013... when Servo was announced. Servo was originally intended to replace Gecko. Anything else is a retcon.

Saying "large parts of that work landed in Firefox" is misleading. A browser engine is a huge thing, and most of Servo is not in Firefox. If you just want to replace a few parts, creating an entirely new engine from scratch is far from the most efficient way.

Why does this matter? Well, because decisions have consequences. Way back in 2013, they were feeling pressure from Chrome, and decided the best way to compete was to rewrite the browser engine (in a brand new language to boot). The original engine stagnated, and here we are 7 years later. What a colossal failure.

Re:Update on Firefox Send and Firefox Notes by dralley on Friday September 18, 2020 @12:48PM (#24519035)
> It was written in 2013... when Servo was announced. Servo was originally intended to replace Gecko. Anything else is a retcon.

Here is a quote from the Servo wiki from 2014, which is the earliest snapshot present in the WaybackMachine archives.

>Servo is explicitly not aiming to create a full Web browser (except for demonstration and experimentation purposes). Rather it is focused on creating a solid, embeddable engine. Although Servo is a research project, it is designed to be "productizable"—the code that we write should be of high enough quality that it could eventually be shipped to users.

https://web.archive.org/web/20140718030420/https://github.co...

The words "Firefox" or "Gecko" do not appear a single time in the blog post you cited originally. This is because there were no plans to replace Gecko with Servo at that point in time. They did plan for that possibility, and it was probably a minor goal, but the primary goal was research, as they stated in both the blog post and the wiki entry. They were hoping that they could replace parts of Gecko, I'm sure, but it was never a given.

Re:Update on Firefox Send and Firefox Notes by btrask on Friday September 18, 2020 @01:22PM (#24519433)
Thanks for taking the time to reply!

In your quote, they didn't want to create a full browser, but they did want to create a full engine. And it was designed to be "productizable." I think it supports what I'm saying.

Servo was the last big plan from Mozilla to turn things around. Since then, we've just gotten Pocket, random bundled add-ons, etc. It seems like they are mostly just content to slide into irrelevance. And I am very sad about that. I do honestly wish Servo had succeeded, although I thought it was pretty obvious it wasn't going to.

Also, while I'm airing grievances, I think it's very likely that having a few big chunks of Firefox/Gecko be written in Rust is going to be a maintenance burden that will slow down development even more. Now that Mozilla has laid off the Rust and Servo people, what are they going to do?

Re:Update on Firefox Send and Firefox Notes by dralley on Friday September 18, 2020 @02:45PM (#24520453)
>Here's the thing though: What this Servo dev thought of as "production ready" and what the Gecko team thinks is "production ready" are very different things. In Gecko-land, it's not enough to do best-practice things like continuous integration, regression tests, error handling, etc. For Gecko, it's also about compatibility -- both with 25+ years of web content (much of it malformed) and a wide range of supported combinations of operating systems and hardware.

>If you're working on Servo, you can be much more strict about what hardware combinations you support and what kind of content renders well. Look, there's a reason that the lineage of all widespread web engines go back 20+ years: it's much easier to incrementally improve that engine while ensuring that you're not breaking anything than it is to start over from scratch.

>I would also like to point out that you don't have to take my word for it: It has taken at least 3 years (probably closer to 4 years) to get WebRender ported over to Gecko from Servo and get it running well enough to the point that we can start saying that it will likely reach 100% deployment within months instead of years.

>My point is that, while Servo was great for demonstrating new ideas and producing eye-popping demos, it was not going to replace Gecko anytime soon, regardless of what those few Servo developers thought. In all the time I've worked at Mozilla, I have never once heard anybody in charge of Firefox say that we were going to do a wholesale swap out of Gecko with Servo.

https://web.archive.org/web/20200815135321/https://tildes.ne...

Re:Update on Firefox Send and Firefox Notes by btrask on Friday September 18, 2020 @03:41PM (#24521081)
Thanks for that link!

We might be arguing past each other. He says this:

> Unfortunately a narrative kind of built up around all this stuff that Gecko developers were a bunch of bumbling idiots who were just maintaining a bunch of outdated bloatware, while the Servo project was where all the action was.

This is precisely my complaint. Firefox really did need some sort of strong direction to save it, and Servo was all they came up with. I don't think it was just a few self-important Servo devs, I think (at least part of) management was in on it too. In fact, the blog post above was signed by Brendan Eich, which I find really disappointing (I thought he, at least, was smarter than that...).

Anyway, once Servo sucked all the other oxygen out of the room, Firefox was really doomed. Now Servo is dead and we have... a few incremental improvements to Gecko to show for it. I definitely feel bad for the guys working on Gecko the whole time. That said, they could've came up with some "response" to Servo, but they didn't.

Re:Update on Firefox Send and Firefox Notes by kevincox on Thursday September 17, 2020 @09:01PM (#24511855)
Never officially. But I think once they started to migrate components into Firefox it seemed obvious that the experiment was a "success" and that it was on the path to replacing gecko (starting piece by piece and maybe eventually making a switchover).
Re:Update on Firefox Send and Firefox Notes by dblohm7 on Friday September 18, 2020 @01:19AM (#24513253)
Mozilla developer here.

The Gecko team was mostly spared from the layoffs. There is no intention to cease Gecko development.

Re:Update on Firefox Send and Firefox Notes by fabrice_d on Friday September 18, 2020 @10:55AM (#24517540)
I really hope this is true, but there as been absolutely zero clear communication from Mozilla VP and above managers about being committed to Gecko. Why is Firefox CTO not writing a blog post about that?
Re:Update on Firefox Send and Firefox Notes by fanatic2pope on Thursday September 17, 2020 @05:58PM (#24510480)
If they switched to webkit there'd be no more reason to use it over degoogled chromium.
Re:Update on Firefox Send and Firefox Notes by xnyan on Thursday September 17, 2020 @10:44PM (#24512435)
Unless there are very significant differences that are noticeable to mass user base, the engine is not a relevant factor in browser market share. When chrome came charging in, Microsoft had let IE fall so far behind that even to my 74-year-old opa, chrome was noticeably better.

People largely don't choose firefox over non-degoogled chrome today. All browsers on iOS are reskinned safari with different accounts for synced bookmarks and tabs, and yet people choose to use different iOS browsers for various reasons, the browser's engine not among them.

It pains me to think about, but from a realpolitik perspective it makes zero sense for Mozilla not to slap an orange fox on chromium and call it a day,

Re:Update on Firefox Send and Firefox Notes by thayne on Friday September 18, 2020 @12:33AM (#24513035)
For me, and everyone I know personally that uses Firefox, the primary motivation for using Firefox is because it uses a non webkit/blink engine, and we want browser diversity. If that goes away we there is a lot less reason for us to stick with Firefox.

Although I suopose there is still manifest v3...

I fear that if Firefox switched to webkit or blink, they might lose a significant number of existing users without a clear way to win back more.

Re:Update on Firefox Send and Firefox Notes by chaosharmonic on Thursday September 17, 2020 @10:13PM (#24512263)
I mean, a WebKit-based Firefox would at least be a distinct engine, and a cross-platform one at that. (WebKit isn't very well-represented on Windows in particular.)

Contrast a Blink-based FF, which would basically just be Brave.

Re:Update on Firefox Send and Firefox Notes by nl on Thursday September 17, 2020 @08:21PM (#24511593)
I wonder what the future is for Rust?
Re:Update on Firefox Send and Firefox Notes by steveklabnik on Thursday September 17, 2020 @09:03PM (#24511868)
Re:Update on Firefox Send and Firefox Notes by nanagojo on Thursday September 17, 2020 @09:09PM (#24511895)
The writing is on the wall at this stage. The current Mozilla have no will to keep maintaining Gecko, which in their eyes is seen as burning money which could be spent on "Product".