{from one of my later replies in this thread}
in my own case, fwiw, of the three i listed, the one at greatest risk of me backsliding, is The Fox... i have tried several times over the years to give up
, & ofc all those attempts failed, coz... i love its icon, & i love getting the bugfixes & new features faster!
...aaaaaaaaand so it has come to pass... i have jumped back to
this morning! 🙄🤦♀️
it's just been bugging me continually over these days since my OP, how it could be that my primary Nightly profile could have suddenly changed, with one routine update several days before my OP, from being great to being shit [as judged by its performance on my primary fediverse tab;
#Phanpy]. i then kept waiting for subsequent bi-daily updates to fix this "obvious" bug the Devs "had introduced" with that specific version, but update after update my Phanpy tab remained unusable [scrolling had become agonising, feeling like it was trying to move thu cold treacle, with attendant high cpu%]. neither regular
nor
suffered this problem [but then again, neither had Nightly, until That One Update].
so coz i'm stubborn & silly, i just could not leave this puzzle unsolved. this morn after many hours investigating, i finally solved it, afaict... for years, Nightly on my pooter has run better when i disable its default settings of Use recommended performance settings, and associated Use hardware acceleration when available [i have no dedicated gpu, only the integrated Intel graphics]. i've run that way so long i'd forgotten about it. this morn i discovered that the Phanpy treacle problem simply vanishes entirely, if i return those settings to default. so, it seems the Devs made some internal change with That One Update, with which my specific departure from default, formerly as asset, became a liability. d'oh! 😲 🤯
#DropbearPooterising #Linux #LinuxWomen #FOSS
#KDELinux #FirefoxNightly #FirefoxSecondSidebar #NativeTreeTabs
