Live data from Hacker News

Fuck It, I'm Going Back to Firefox

gizmodo.com

271–280 of 654 posts

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

#273

Earlier quoted context omitted.

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 includ…

I regularly have several hundred tabs open in Firefox with no problems. Some people may think this is crazy or messy but I find it very useful for organizing the various projects I'm working on for different clients and my own personal projects. Tab groups and delayed loading make it all very smooth. Such usage is just not possible with Chrome. I tried to switch to Chrome but couldn't find the features I needed and d…

For me I keep tabs open in case I need to go back later. This works except I only end up reusing 20% of the tabs that I opened.

What would be awesome is some sort of auto tab closer that assumes you'll never use the tab again after 15 minutes of idle time.

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

#274
He mentioned it briefly in the article, but I'm now finding safari to be a great browser on OS X Yosemite. It's seemingly fast/faster than chrome, has great retina and media support (Netflix without plugins!), integrates well with safari on my iPhone, but not mentioned here otherwise? It has better aesthetics. It got really good looking in a way that makes all the other browsers look super dated. Who cares about a cloud to butt plugin? I've got privoxy + 1password, don't need anymore than that.

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

#275
post #215

Earlier quoted context omitted.

Shadertoy is a good test case for this: https://www.shadertoy.com/browse Compiling all those shaders is rough on any browser, but only Firefox gets its entire UI blocked. Even Internet Explorer manages to isolate the jank to one tab.

Chrome 1+, IE 9+ and Safari 7+ spawn child processes with less permissions ("sandbox") for almost every tab. Sadly Firefox 39 (nightly) still has no real multi process support. There are only two processes, the main process holds all tabs, the single child process "plugin-container" holds all plugins (Flash, Acrobat, etc.). It's a bit disappointing to see such little progress since 2010. Hopefully Mozilla's Rust base…

[deleted]

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

#276

The worst part about chrome for me is that I can't access my Gmail accounts through Chrome. That's right, I have to use Firefox to access Google's own product because Chrome won't play nice with my school Google Apps account that my school provided us for email. Whenever I try to get to my school account it redirects to the gmail account I used to sign into Chrome - this happens regardless of whether I try to access…

I share your pain. One way to get around it is to use the Chrome 'multiple profiles' feature, it lets you switch to a different 'profile' with entirely different cookies, cache, etc., and will let you sign into a different Google account than in your first profile. You can switch profiles and even have different profiles active in different Chrome windows, without restarting Chrome. https://support.google.com/chrome/…

I think profiles are a hard-to-discover feature. But once I discovered them, I really liked them.

They help me to separate my work and personal everything. Not just email, but my tabs, bookmarks, saved passwords, extensions, etc.

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

#277

Earlier quoted context omitted.

This is probably b/c most people at Google use computers with 32GB of ram.

This might sound silly to some, but I wouldn't be surprised if Google limited its usability tests to high-end machines with RAM in the double-digits. I reckon most programming teams have this issue, since even if they're dogfooding, they're doing so on high-end hardware, meaning that low-end hardware is untested and often unusable. Google isn't the only culprit; many websites nowadays will start to lean heavier towar…

I have 16GB and regularly have >100 tabs open in Chrome.

It works, kind of, as long as I don't try to run anything else at the same time.

The article persuaded me that Firefox may be worth a try again.

As for testing - you'd think testing on a range of hardware would be standard.

Testing exclusively on top spec machines is just unprofessional.

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

#278
In my experience I stayed with Firefox after I learned about tab groups. Sure you can run an extension on Chrome to do the same (and you can run extensions on Firefox to do things Chrome does) but after seeing just how much extensions can bog down a browser I prefer to run mine as close to vanilla as possible.

It's not even "if you download a poorly made extension your browser will be slower" but it seems like extensions have that effect in general. It's probably irrational but I've honestly seen a lot of the most popular extensions falling into this category, extensions like AdBlock and HTTPS Everywhere come to mind.

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

#280

Earlier quoted context omitted.

Superfluous RAM use hurts battery life a lot. Using Safari over Chrome easily saves 2+ hours for me.

> Superfluous RAM use hurts battery life a lot Do you have a reference for why this should be? A quick search yields results suggesting only the opposite (for instance, https://superuser.com/questions/738848/does-more-ram-usage-c... ).

More ram in use generally means more javascript crap running. Which means higher cpu/energy use. Its not the memory use its what is using the memory.
Post reply on HN