Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Fuck It, I'm Going Back to Firefox

gizmodo.com

Post reply on HN
Print view View original

191–200 of 654 posts

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

#191

Post by abetaha »

tashoecraft wrote: post #38
nostromo wrote: post #14

I recently switched to Safari for similar reasons. Safari is much faster than it used to be. It's also tightly integrated with my phone, including password management functionality (similar to LastPass) that works on all my devices. You can also get AdBlock for Safari now, which wasn't always the case. It also has a snazzy built-in RSS reader and just looks better than Chrome.

Exactly, Safari handles 90% of web needs and doesn't clog up my memory the way Chrome does. It handles my battery exponentially better then Chrome as well. Then with adblock plus, lastpass and pocket I'm all set on extensions.

I have seen my battery life improve from 3 hours while using Chrome to 5 hours while browsing the same content using Safari on my MacBook pro. One downside I've experienced with Safari is that it does not reclaim the memory a tab uses after it is closed, which leads to a crash once a day.

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

#192

Post by basicguru »

This article is full of whiny nonsense. Sounds like one of those rants you hear from those who think they are savvy because they can install apps on their phone. Chrome eats batteries for lunch, but it's still super fast and stable, and I use quite a few 'useful' addons.

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

#193

Post by emodendroket »

FilterJoe wrote: post #177
gvb wrote: 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 includ…

I imagine this has something to do with the sandboxing in Chrome that prevents one tab from causing the entire browser to crash, no?

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

#194

Post by jackmaney »

FilterJoe wrote: post #177
gvb wrote: 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 includ…

I switched from Firefox to Chrome right around Firefox 3.6. I have an average of around 20 tabs open at any given moment, and I tend to go around a week or two between reboots.

Other than the occasional tab crashing and quickly reloading (and by "occasional", I mean maybe once every couple of months or so), I've never had an issue with Chrome. It just works.

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

#195

Post by jaredsohn »

mtrimpe wrote: post #109
gear54rus wrote: post #4

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?

Chrome doesn't run Adobe Flash; it runs its own version called PepperFlash by default. I know because I witnessed them breaking one Flash video-recording feature after the other trying to reimplement the damn thing...

>Chrome doesn't run Adobe Flash

Yeah, it does. Pepper Flash is just Flash repackaged to use Chrome's new plug-in architecture; it is still written by Adobe. (Although perhaps Chrome does deserve the blame for some crashes related to how it integrates with the browser.)

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

#196

Post by inclemnet »

Outofthebot wrote: post #169
Zombieball wrote: post #155

Earlier quoted context omitted.

> doesn't clog up my memory the way Chrome What exactly is "clogging up memory" that everyone here complains about? I can understand if Chrome is using 6 / 8gb of your ram and you are simultaneously running photoshop and it can't grab any memory due to Chrome, but is this the case? Shouldn't Chrome use as much RAM as it can to ensure speedy performance provided its not starving out any other applications? I have litt…

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...).

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

#197

Post by gknoy »

zer0defex wrote: post #163
nvk wrote: 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.

This. I use Firefox specifically because it allows you to set history to NEVER be remembered. Really wish Safari did the same...

Why not just always open Incognito windows?

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

#198

Post by shmerl »

> Remember when we all switched from Firefox to Chrome?

I remember the hype, but I never switched. Firefox was always good enough for me. And really, Firefox overtook Chrome in performance a while ago already. And naturally Mozilla's manifesto is way better to support than Eric Schmidt's "you don't need privacy if you have nothing to hide" idea.

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

#199

Post by lttlrck »

joesmo wrote: post #72

The issue that has me considering a switch is that the latest Chrome dev tools' network panel tries too hard to show a preview of JSON requests that are not JSON. When I get exceptions and such, they come through as HTML or plaintext, sometimes with JSON at the end. Previously, Chrome would realize that it's not proper JSON and render the HTML. Now it doesn't render the HTML preview, but does render the JSON which is…

Did you report it?

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

#200

Post by bdcravens »

What drives me nuts is the fact that even after I explicitly close it, Chrome insists on opening up all the tabs I had open before. Reloading those tabs takes time, and I can only pray it's not some poorly coded webpage that performs an undesired action based on the URL. If I explicitly close an app, my expectation is that all the resources I had open close as well (to be fair, Atom does the same thing)
Post reply on HN