Benchmarking Firefox 83 Nightly With "Warp" Against Google Chrome On Linux

[Brane215]

You mean like webassembly? Or what exactly do you have in mind?

Like what Webassembly should have been.
I 've had in mind "browser" exposing standardised container with basic and optional libraries and having a protocol to download starting "module" that could initialize stuff and dload rest of the application SW. All using efficient binary protocols from ground up, for example.

[tenplus1]

I'm starting to wish that Mozilla would work on a front-end for the chromium engine and go the way of Internet Explorer, only this time de-google everything and make a better gui that doesnt spy and report back to anyone.

[Tvashtar]

Maybe there is some debug tarpit active in the alpha builds? It would be great to have at least two common tests on PTS and Mozilla's treeherder for some reproducibility sanity check.

There are, multiple, javascript_async and jsgc_poisoning are the ones impairing js, it's possible to turn them off. It was mentioned before but Michael keeps ignoring that.
Guess we'll have to wait for stable for some sanity

[yuyichao]

Um, so you're saying that the way modern agile software development works is that for every development branch, they first add shitloads of debug stuff that slows everything down, without adding any options for turning it off? Then, at the end of the release process, they quickly remove all the debug stuff and the bugs, and compile a shiny slim production version that nobody could build from the intermediate states? Sounds like a plan.. not. The thing is, there's simply no need to break absolutely everything before every new release.

No, I believe what he was saying is that those options are always there but when you grab the nightly **build**, those are built with the debugging options enabled since, well, these build are for debugging. There's no flipping back and forth, just two completely different build configurations.

-----

At least that's what I understand he was trying to say. I don't know if that's actually the case for the official nightly binaries (though it would make sense) or if those binaries are exactly what's used in the test.

[andyprough]

According to Trinity College researchers, Chrome is the worst offender in terms of default phone-home behavior when compared to Firefox and Brave. Chrome by default logs users keystrokes as they are typed, tracks them with unique device identifiers, and tracks users beyond browser restarts and even beyond browser reinstalls. The best of the 3 was Brave, which did not phone home any identifying information. https://www.welivesecurity.com/2020/...privacy-study/

[rabcor]

So chrome is generally much faster than firefox, and the current firefox nightly builds are major regressions performance wise, great....

[jrch2k8]

WoW, what a load of conspiracy theories.

1.) Chrome is not IE, IE holded that massive market share because Microsoft on purpose broke all web standards for a long time, so any other browser will fail to render <-- this is well documented technically and litigiously.

2.) Sites that fail to render most of the time (if not all) is because it uses standards BUT those still aren't supported by Firefox while they are supported by Blink and a bit less by WebKit(i had this happening on Safari some times as well)

There is no big anti FOSS conspiracy here, Firefox is not up to par with Chrome(ium) simply because of Firefox/Mozilla keep spreading efforts all over the place trying to get the next big thing but never actually finishing anything properly, so at the end of the day Firefox have less CSS support, partial GPU acceleration, slower JS, etc. etc. but hey they used all that time on an OS that never went anywhere and using a new language to fix all the previous but turns out the miracle didn't happens and still have all the same problems, etc ,etc.

On the other hand Apple and Google took that time to polish the living bejesus out of every subsystem in their browser and as expected are now ahead.

If Mozilla want to stay alive, they need a project manager and start focusing on fixing stuff properly instead of being an incubator of dozens of partial ideas. In my opinion Mozilla should freeze the current Firefox tree as LTS and rewrite the damn thing from scratch with a very laser focus set of features in a modern clean and tight fashion and then start improving support for other stuff instead of keep dragging quarter a century of useless baggage around.

[leipero]

Is there any particular/valid reason why people use Chrome rather than Chromium on GNU/Linux? I know some "features" are missing, such as ancient codecs, WDRM and tracking, but considering the fact that Chromium is free and open source and available in most major distributions repositories, why not using Chromium instead?

I don't know if netflix works on Chromium, that was a valid reason in the past, but it didn't work on Firefox, and now it works (I believe), so it should work on Chromium as well.

[creoflux]

And the damnable thing is....FOSS is being used to drive out freedom and choice in the very FOSS world we cherish. And everyone accepts that either out of sheer ignorance or apathy. Giant Corporations and their paid for Governments that shield them are the very ones building us "free barns" to house their products. And the products are...us.

The "Animal Farm" of the future will be arguing about the color of grass from our "free barns". That one over there is Baaaaaaah!

[Jumbotron]

I was a Firefox user around the time of its first stable releases, and thought there was no reason to use anything else.

Then sometime later, I switched to Linux and KDE and noticed that Konqueror was like lightning compared to Firefox. I was excited when Chrome decided to adopt KHTML and thought more browser competition would be good.

Little did I know that it would lead to a Chrome monoculture. I fought against it on principle by switching back to Firefox just before they started doing rapid releases.

I felt that Firefox had an exciting future and that it was going to compete adequately.

But Big Tech pushed through new web standards at a blinding pace, and Mozilla didn't get ambitious with projects like Servo until far too late.

The unbeatable features Mozilla offers like Multi-Account Containers are a power user feature that would not be usable by most.

The added security of Rust is not something most users care enough about.

Mozilla failed to win with FirefoxOS and VR and every other initiative they tried.

As much as I prefer a diverse browser ecosystem, they should honestly just throw in the towel with gecko. Switch to blink and become a privacy focused brand. They already gave up on almost all the exciting blue sky projects that I care about.

I only still use Firefox out of habit now. Might switch to Falkon.

I agree with everything you said...except throw in the towel and rebase Firefox to Blink. See my reply above to scottishduck. He made the suggestion of rebasing to Webkit. I think that is wonderful idea.

Mozilla is bleeding to death. Cut loose Rust. Cut loose Servo. Just as Microsoft threw in the towel with their homegrown IE and Edge code base and decided to just rebase around Blink and Chromium, Mozilla needs to tack in the other direction and team up with Apple and Webkit just like Gnome did with Epiphany, now called Gnome Browser. Mozilla just needs to cut everything loose and made the best damn Webkit based Browser on the planet....even faster than Safari. That could give them a lifeline.

Because let's face it....it's an Apple and Google world now. Even with browser frameworks. Webkit and Blink which is a fork of Webkit.