News for hackers. Stuff that matters.
Re:RenderingNG: An architecture that makes and keeps Chrome ... by art0rz on Thursday October 07, 2021 @03:46AM (#28783363)
To me it feels like bloated browser profiles makes the browsers sluggish.

I get annoyed with how slow Chrome is, so I switch Firefox. After a while the Firefox profile gets bloated and I get annoyed and switch back to Chrome with a clean profile and it feels really quick again. Ad infinitum.

Re:RenderingNG: An architecture that makes and keeps Chrome ... by pabs3 on Thursday October 07, 2021 @03:49AM (#28783391)
The Firefox profile manager and Chrome temporary files would let you test this theory.
Re:RenderingNG: An architecture that makes and keeps Chrome ... by ksec on Thursday October 07, 2021 @06:55AM (#28784643)
I dont understand how profile could make such a difference but that is also my experience as well. Everything is fast in a clean profile.
Re:RenderingNG: An architecture that makes and keeps Chrome ... by jd3 on Thursday October 07, 2021 @11:33AM (#28787662)
On Firefox, if you have an unbelievably large number of entries in your History, Bookmarks, and/or Downloads (your Firefox "Library" — chrome://browser/content/places/places.xhtml), you could theoretically become limited by insert/update performance in Firefox's embedded sqlite, I believe.
Re:RenderingNG: An architecture that makes and keeps Chrome ... by mavhc on Thursday October 07, 2021 @07:18AM (#28784798)
The fix for 99% of firefox problems is: firefox -p, make a new profile