I have seen folks talk about a pain point for using FF (or forks) being related to YouTube being super slow. The about:config settings the article mentions did seem to lead to YouTube loading faster on both my FF and Zen-Browser installs. So maybe this might help for others that specifically don’t like to use FF as their main browser because of YouTube.
For those that just want the settings:
gfx.webrender.compositor.force-enabled (set to true and restart FF)
If on AMD GPU, this extra setting is supposed to help reduce CPU usage:
media.wmf.zero-copy-nv12-textures-force-enabled (set to true and restart FF)
*edit - per Zak in the comments. The AMD setting is Windows specific.
It really is a shame that Microsoft gave up their technical position in order to gain a market position. However, ultimately, that worked out for them.
Microsoft didn’t keep it because developing a web browser is insanely expensive, and they where too far behind. While they where trying to pivot to Azure and other cloud ecosystems.
With likely 1000+ engineers being involved in Chrome in a meaningful way, it’s an insanely expensive project, and Microsoft just couldn’t keep up.
Now given that Mozilla has an engineering team 1/4 to 1/6th the size for Firefox really puts into perspective How astronomically well they have been doing with Rust.
This also puts into perspective how unlikely other browsers like Ladybird are to ever take off, when a year of their development is eclipsed by a few weeks of major browser development. Compounding over and over.
Shits a mess.