Re:Our Year in Review: How We’ve Made Firefox Faster in 2020
by franga2000 on Wednesday December 16, 2020 @03:54AM
(#25440383)
If it doesn't automatically enable it for yout (check about:support), try force enabling WebRender. It made things much better for me both on Wayland and X11 for the past year or so. I don't know the about:config option, but some googling (ducking?) should get you some instructions.
And out of curiosity, what's your current problem with Wayland+Nvidia? For me, it's been pretty much equally as unstable as it is on X.
Re:Our Year in Review: How We’ve Made Firefox Faster in 2020
by Shared404 on Wednesday December 16, 2020 @06:43PM
(#25450330)
> ducking?
I've been using "DDG" as a stand in:
"If you DDG it you should find some references"
It's not perfect, but at least on tech focused sites where the readership knows about DuckDuckGo I've found it works.
Re:Our Year in Review: How We’ve Made Firefox Faster in 2020
by franga2000 on Thursday December 17, 2020 @03:16AM
(#25453674)
Yeah, that makes more sense. I've used it before too, but when I was writing that, my brain just completely failed at remembering it :)
Re:Our Year in Review: How We’ve Made Firefox Faster in 2020
by Epskampie on Wednesday December 16, 2020 @06:36AM
(#25441425)
Thanks, I already tried that once before and it didn't really make a difference, will try again.
On GNOME you can't use wayland if you're using nvidia's binary driver, which I am.
On windows it’s solid however!
Edit: just saw this in the release notes for 84: “ Additionally we'll ship an accelerated rendering pipeline for Linux/GNOME/X11 users for the first time, ever!”
Fingers crossed, gonna check it right away!