Here is a large history causing slow load times; https://bugzilla.mozilla.org/show_bug.cgi?id=223476
Here is their recommendations regarding download history, which I myself have experienced (too many downloads remembered forever slows down the browser) https://support.mozilla.org/en-US/kb/firefox-hangs-or-not-re...
There is nothing inherent in the design of A hypothetical browser that would make it slower over time, its just a matter of people make assumptions and those assumptions are often wrong, and then performance suffers.
The support page lists "Extensions and themes, website-specific preferences, search engines, download history, DOM storage, security settings, download actions, plugin settings, toolbar customizations, user styles and social features will be removed."
[1]: https://support.mozilla.org/en-US/kb/reset-firefox-easily-fi...
1. “(Firefox|Chrome) is slow” 2. “Did you try removing Ad-Block Plus, etc.?” 3. “Now it's fast again!”
I think we're well past the point where the browsers are going to need to start having some UI around monitoring and exposing slow extensions to make it easier for users to learn this.
I also use Aurora which is still super fast to me. I also develop with Chrome Canary and the stable Chrome version. Canary has times when its totally useless or when someone breaks the build and I can't use it for a week so until the next update comes out.
All in all, yes, less overhead means a snappier browser to me.
Of course, if you don't want that, you're sweet.
I've been using $RELATIVELY_FRESH_BROWSER_INSTALL again recently. I stopped when it was slower and less stable than $BROWSER_I_HAVE_NOW_BEEN_USING_A_LONG_TIME.
These days it often feels faster than $BROWSER_I_HAVE_NOW_BEEN_USING_A_LONG_TIME.