The reliability of Firefox's post-crash 'session restore' is what made me stick with it for good over Chrome. Life of a power tabber.
Fuck It, I'm Going Back to Firefox
21–30 of 654 posts
Re: Fuck It, I'm Going Back to Firefox
#22Something I noticed the other week - Chrome on Windows will scan my desktop on startup (all the icons go back their generic version, and then return). Why would they do that? My desktop isn't where the cache is.
Re: Fuck It, I'm Going Back to Firefox
#23Did the same.
Re: Fuck It, I'm Going Back to Firefox
#24The 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.
They want to make their little OS inside your current OS, so that's it, they introduce accounts, users, apps, notifications... Meanwhile most people (including me) just want to browse the damn open internet.
To be fair, the trend of the browser usurping the OS has been going on for years. Any browser that wishes to stay modern and competitive has no choice but to leverage the inner-platform effect to a full extent.
Re: Fuck It, I'm Going Back to Firefox
#25Earlier quoted context omitted.
exactly!! I don't want Google everywhere.That's why I changed the default search engine to duckduckgo. Let's see how it goes.
Funny, that's part of why I use Chrome. Having all my Google accounts and apps available is a huge feature to me. Plus Firefox crashing is a huge downside. As for privacy implications, there's no reason to believe Google does anything inappropriate, and I rather like having my internet experience tailored based on past behaviour. To each their own I guess.
Sure, some people may like that. All I ask is a reasonable way of opting out.
Re: Fuck It, I'm Going Back to Firefox
#26I run Chrome with
"C:\Program Files\Google\Chrome\Application\chrome.exe" --renderer-process-limit=9
and it's much better that way: Less total memory consumption and killing a renderer unloads many tabs at once.
It seems to me that the focus on security by isolating every webpage from each other went to far recently. When I started with Chrome I think they used to limit the maximum amount of render processes much more. Of course if there was a serious security hole in e.g. webkit/blink then one tab could have stolen data from another tab more easily. But it consumed much less memory
Re: Fuck It, I'm Going Back to Firefox
#27Did that last year and couldn't be happier. Whether performance and memory use is better or worse, I've grown wary of Google's pervasiveness.
Re: Fuck It, I'm Going Back to Firefox
#28The 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.
How did you loose data that way?
And I agree 100% with you!
Re: Fuck It, I'm Going Back to Firefox
#29I have some serious issues with Chrome (the permaloading, it's new download blocking 'feature', poor startup time), but I did not find Firefox remotely an improvement. On my system it is half as fast, twice as buggy, and even more memory hungry than Chrome is. I think people overstate Chrome's memory usage as a factor of performance; IME it's still less than FF in total most times, and largely that memory cost doesn'…
What makes Safari a toy?
Re: Fuck It, I'm Going Back to Firefox
#30Something I noticed the other week - Chrome on Windows will scan my desktop on startup (all the icons go back their generic version, and then return). Why would they do that? My desktop isn't where the cache is.
I believe it is hooking the explorer launch process not 'scanning' the desktop. But I may be wrong. Like the author I got tired of all the issues I was having (exactly two extensions, OnePassword and Evernote) and switched to Firefox.