Live data from Hacker News

Fuck It, I'm Going Back to Firefox

gizmodo.com

1–10 of 654 posts

Re: Fuck It, I'm Going Back to Firefox

#2
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 piling up. And when I have many windows open it is slower, and when Flash is running, it often crashes. I've switched back to FireFox.

Re: Fuck It, I'm Going Back to Firefox

#4

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…

I never switched to chrome since it seemed sub-par all that time (reduced set of controls, dumbed down all the way) but flash-related crashes are Adobe's problem actually (I also have them on FF sometimes).

When will this proprietary crap die off already?

Re: Fuck It, I'm Going Back to Firefox

#7
The 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

#8
My only beef with Firefox is multiple webpages don't render well for me, but those pages render fine in Chrome and IE.

I haven't stop once to debug why (I just switch to Chrome but sometimes do report the websites to Mozilla), can the reason be in Firefox being more pure and the others browsers allowing more quirks? If this is the case, isn't this bad UX?

Re: Fuck It, I'm Going Back to Firefox

#9
I 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

#10

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.

Post reply on HN