Live data from Hacker News

Fuck It, I'm Going Back to Firefox

gizmodo.com

171–180 of 654 posts

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

#171
post #112

Earlier quoted context omitted.

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?

You do realize that Chrome is different from Chromium, the open source browser, right?

I guess yes. What difference does it make in the context?

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

#172

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…

There is any browser that tolerates flash properly?

My associate had a machine that would RESET because of flash (we know it is flash because it would only start to randomly reset if flash was running somewhere on the machine), no matter what browser.

And in my personal experience flash could crash ALL browsers open at once, one time flash crashing on MSN Messenger partially froze my entire machine, after 10 minutes wrestling it to get to the task manager (yep, sometimes I am stupid) and close flash process, the machine came back to normal.

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

#173
I made the switch a few months back when I got a new computer, but found that Firefox was slower for me with less extensions than Chrome (on mac).

That being said, I keep the number of extensions I use low: json formatter, a rest client, adblock, cloud-to-butt, clearly, and pocket. Chrome works a lot better with multiple windows open in my experience (on a new iMac with 2 external monitors).

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

#174
post #162
post #34

Earlier quoted context omitted.

To be fair quite a few users left Firefox because they found it "bloated" or "it didn't work anymore" but never realized they were the ones that installed the bloat/adware/malware.

I left Firefox because it was measurably slower than Chrome at the time (and not by a small margin) and because crashes/hangs would usually take the whole Browser down.

This. Have the scales tipped the other way recently? Chrome still feels faster to me, but I only have one active extension (Ad Blocker).

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

#175
Ironic that shortly after reading this, chrome crashed on me. I've only got 2 extensions loaded other than the 3 Google doc ones that came pre-loaded.

One thing I did notice the other day is that chrome will reload webpages on it's own even if they don't have focus. I was running an express.js app on localhost and periodically I would see traffic in in the logs even though I wasn't interacting with it. It may just be enforcing some ttl/cache header that was automagicly set, but it will make me close my browser more often.

It might be worth installing firefox and see if it behaves the same.

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

#176
post #81

My biggest reason for not using Firefox is that I always keep 2 browser windows open in Chrome, one is for my work account and the other is for my personal account. I like this separation. IIRC you can't have 2 profiles open at the same time in Firefox and even switching between profiles is not easy. I do use Firefox on my personal laptop, but I spend 8 hours a day on my work laptop and need this feature.

firefox --new-instance --ProfileManager

Good to know. Only thing remaining would be a way to distinguish between them.

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

#177
post #15

I read the article hoping for something insightful, but when I read the paragraph ...a half-dozen tabs that auto-open on launch thanks to the dozens of extensions I've accumulated over the years[...] I had to stop and say "wait, what?" To leverage his analogy that it is like coming home to a new house to find that most of your stuff is already there, it is like not cleaning your house and not taking out the trash for…

The problem is using many open tabs with Chrome. If you use no more than 3 or 4 tabs, Chrome is generally fine. If you use more than that, Firefox has some built-in features to help with tabs such as delayed tab loading and tab grouping. It also has more and better extensions for helping with multiple tabs. Furthermore, it doesn't launch a new process for each tab.

In a browser comparison I wrote last month, I included a section for users who like to keep a lot of tabs open. Even Opera, which uses the same code base as Chrome, does tabs better than Chrome:

http://www.filterjoe.com/2015/01/23/best-browsers-2015-which...

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

#178
post #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.

You should probably understand this: Google doesn't give a shit. The total market share of people who care about whether or not their browser is linked with their Google account is probably less than one percent. The value they get from knowing everything you do online? I'm not sure how you'd calculate that, but I'm positive it's greater than losing the tiny number of hackers who are protective of their personal data…

You're right. We can add this (already predictable) aspect to our visions of the future where we get into our self-driving Googleobile that on startup signs into our Google accounts...

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

#180
I just tested Firefox 37 (Developer Edition) and Firefox 38 (Nightly).

The multi-process "Electrolysis" support in 38 is great. Several tabs with flash plugin work fine now, without slowing down the whole browser. Though, I still see only one main process for all web sites (there is a child process "plugin-container"), that's a bit disappointing. IE 9+, Chrome and Safari 7+ spawn a new process for every x sites - a child process with little permissions (a technique known as "sandbox"). Maybe we have to wait a little longer for Mozilla's Rust based Servo engine.

Post reply on HN