Floorp VS firefox-performance-dashboards

How to enable Firefox's native Dark Mode: https://github.com/Floorp-Projects/Floorp/discussions/487

I'm using Brave with rewards, vpn, wallet disabled and around 20 flags modified. It works much faster, better extension support for me with fewer bugs, less memory usage when fewer tabs are opened. I chose brave because it can sync.

I'm impressed with Firefox and tried a fork called floorp. It has some useful additions and find it better than regular Firefox while still supporting sync and was using ungoogled chromium before.

https://github.com/Floorp-Projects/Floorp/releases

Unfortunately some websites still work better with chromium browsers in my experience. This is anecdotal but I also feel some negative fingerprinting from Google owned websites on Firefox, more memory leaks as well. It's only a matter of time before I change to Firefox (forced manifest V3) but I will stick with brave for now.

Your machine seems to have very low RAM. Nowadays, at least 16GB RAM is recommended. Alternatively, try out Floorp Lightning: https://github.com/Floorp-Projects/Floorp/releases/tag/v11.5.1-lightning

Firefox does have native Dark Mode, it's the fastest Dark Mode ever exists, in fact it doesn't even reduce performance like Dark Reader and Chrome's Force Dark Mode, but it needs some cares to be more usable, check: https://github.com/Floorp-Projects/Floorp/discussions/487

There is no Android version for Floorp yet, atleast officially that I know of.

For windows download the win64 installer from https://github.com/Floorp-Projects/Floorp/releases

> Show me these pages that Firefox doesn't render well.

I'm not doing homework for you. Lots of pages don't render well in Firefox, it's a well known issue which is why it comes up in every thread about Firefox.

> Show me pages that tank Firefox performance.

Firefox in general performs poorly. Again, known long-term ongoing issue. Look at this thread where almost every top-level comment is sceptical that Firefox is even close to Chrome in performance: https://news.ycombinator.com/item?id=36770883

You can find ongoing performance benchmarks between Chrome and Firefox here, and it's not flattering for FF: https://arewefastyet.com

> How many of them will have -webkit-* and other engine-exclusive markup/CSS?

I don't care, at all. It's not my job, as a user, to debug performance problems.

> Firefox updates every 6 weeks, just like Chrome.

Ok? I didn't say anything about update cadence.

The link is terrible. Maybe the article should link to https://arewefastyet.com or maybe the Speedometer selection at https://arewefastyet.com/win10/benchmarks/raptor-desktop-spe...

Well I would wager a guess it's due to consistency. The full site includes a bunch of different benchmarks, with a lot of them having the y axis as execution time in milliseconds. Meaning, lower is better. They probably just wanted to keep that consistency even with tests that use scores. Definitely a bit misleading without the full context. The full site is arewefastyet.com

They do... They just don't have the resources Google does. If you see https://arewefastyet.com you can see that Firefox has been steadily improving in speed, and they have actually recently been working to make react faster.

I filed a bug for that.