This has been exactly my experience. I was an early convert to Chrome, and I loved how fast it was, but now I find it slow and buggy. There are some partial workarounds: Chrome does a cache lookup on your history when you type, so if you delete your history, then you get a speed bump. But I'm annoyed that I have to erase my history. If I never erase my history, Chrome gets very slow after a few months of history pili…
Its been my recent experience too, I keep a lot of tabs open and began to notice Chrome was filling up my memory. Very strange that Google let the situation get so bad. Mind you I find the Chrome developer tools far more powerful and intuitive than those in Firefox which stops me moving entirely.
Fuck It, I'm Going Back to Firefox
51–60 of 654 posts
Re: Fuck It, I'm Going Back to Firefox
#52I have tried it many times but failed. The reason - if firfox memory goes too high, which happens frequently, there is no option to kill single tab(in the stable version) like Google Chrome. I have started using Firefox Nightly (because of separate process feature) but it keeps on crashing. So I am ready to jump on it as soon as we have new stable build with separate process for each tab.
Re: Fuck It, I'm Going Back to Firefox
#53Re: Fuck It, I'm Going Back to Firefox
#54The biggest issue I have with Chrome is how aggressive it's been about linking Google IDs with the browser. I've lost data twice by bugs related to not having a linked ID. Please Google, understand this; I don't want my browser linked with my Google account.
Re: Fuck It, I'm Going Back to Firefox
#55Earlier quoted context omitted.
They are free to that, just please give me a reasonable way of opting out.
It's called Chromium.
Also, chromium seems to be getting less and less care from google now. See this bug for example which prevents using screenshare in hangouts: https://crbug.com/416856
Re: Fuck It, I'm Going Back to Firefox
#56The reliability of Firefox's post-crash 'session restore' is what made me stick with it for good over Chrome. Life of a power tabber.
Re: Fuck It, I'm Going Back to Firefox
#57The reliability of Firefox's post-crash 'session restore' is what made me stick with it for good over Chrome. Life of a power tabber.
Re: Fuck It, I'm Going Back to Firefox
#58The biggest issue I have with Chrome is how aggressive it's been about linking Google IDs with the browser. I've lost data twice by bugs related to not having a linked ID. Please Google, understand this; I don't want my browser linked with my Google account.
Being that I'd never intended to 'sign into Chrome' in the first place (the form looks awfully similar to the gmail login), I essentially rage-quit Chrome and haven't looked back since. I've embraced Firefox and I feel better using free and open source software.
Performance has been excellent. The only thing I regularly notice is that many startups seem to only QA their products in Chrome.
Re: Fuck It, I'm Going Back to Firefox
#59Re: Fuck It, I'm Going Back to Firefox
#60This has been exactly my experience. I was an early convert to Chrome, and I loved how fast it was, but now I find it slow and buggy. There are some partial workarounds: Chrome does a cache lookup on your history when you type, so if you delete your history, then you get a speed bump. But I'm annoyed that I have to erase my history. If I never erase my history, Chrome gets very slow after a few months of history pili…
Its been my recent experience too, I keep a lot of tabs open and began to notice Chrome was filling up my memory. Very strange that Google let the situation get so bad. Mind you I find the Chrome developer tools far more powerful and intuitive than those in Firefox which stops me moving entirely.
I had this problem too and found that Chrome was getting so slow that it was unusable. For those who have this problem and don't want to switch from Chrome there is an extension called "The Great Suspender" which dumps background tabs after a configurable time period of inactivity. It helped immensely.