These two tweaks should improve Firefox's performance on YouTube significantly - gHacks Tech News
www.ghacks.net
Here are two quick tweaks for improving the performance of the Firefox web browser on YouTube.

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.

  • d-RLY?@lemmy.mlOP
    0·
    2 months ago

    Very true, I hate that so many sites will sometimes fully load on FF and start to work right before a fake error message telling me to “try updating FF to a newer version” (even though they know it is fully updated and just want to force opening a Chromium-based browser). It doesn’t help that basically all the browsers (aside from FF, forks of FF, and Safari) are all using Chromium.

    While some of them are very good, and make some actual changes for the better. It still re-enforces Google to basically pull what Microsoft did with IE. IE would probably still be alive and fucking with the internet if Microsoft had done what Google has pulled off.

    Even though original Edge was wonky, it kind of sucks that Microsoft didn’t keep their own shit. But only just because it would be one less major Chromium browser (only good thing currently is that they still allow full uBO).

    Though I really hate their overlaid shit Edge puts on the Chrome download site, and the huge banner at the top of Bing search results page when searching for Chrome. I have to download Chrome on peoples’ PCs a lot at work, so that shit is mildly infuriating to constantly see.

    • douglasg14b@lemmy.world
      0·
      2 months ago

      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.