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

421–430 of 654 posts

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

#421

Post by yellowapple »

muze wrote: post #312
silverbax88 wrote: post #301

Earlier quoted context omitted.

I would ask you to open up your task manager and try picking the largest-in-memory Chrome task and kill it, then see if you still think they are completely isolated. I agree with your point, but give it a shot.

I don't think that's really fair, the largest Chrome task in memory isn't a tab or extension. Yes I suppose it isn't perfectly isolated and if something happens to the main program task it will obviously cause problems but if a single page or extension crashes everything else lives on.

It's a perfectly fair point. The fact that the largest Chrome task by far is not a tab or extension at all, but is the core of Chrome itself, indicates that maybe - just maybe - Chrome isn't doing as good a job of keeping things isolated as it should. That process shouldn't be doing a whole lot beyond driving the UI and managing the lifecycles of its children.

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

#423

Post by Sgt_Apone »

hjeldin wrote: post #290
unreal37 wrote: post #206

Earlier quoted context omitted.

What do you mean "turned into"? Gizmodo describes itself as a "Technology blog focused on gadgets."

Well, they have editors, writers and so on...do blogs have the same structure as news outlets?

There is a lot of editorial guidance for many of the more popular blog sites including the Gawker network. Most of the popular blogs, outside of one-man operations, work in a similar manner.

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

#424

Post by mitchty »

inclemnet wrote: post #394
mitchty wrote: post #280

Earlier quoted context omitted.

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.

So...the claim is that chrome runs a lot more javascript than safari?

I'll phrase it more that I see significantly more memory use in Chrome for long lived processes than I do with Safari.

That said, eventually both get to 6g of ram in use and a restart is needed anyway.

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

#425

Post by mitchty »

inclemnet wrote: post #394
mitchty wrote: post #280

Earlier quoted context omitted.

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.

So...the claim is that chrome runs a lot more javascript than safari?

I'll phrase it more that I see significantly more memory use in Chrome for long lived processes than I do with Safari.

That said, eventually both get to 6g of ram in use and a restart is needed anyway.

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

#426

Post by finishingmove »

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…

The main reason I stuck with Opera 12 is how well it handled dozens of tabs (I remember counting 96 in a long-lasting session). Yes, the memory usage was high, but it never felt slow. After switching to the new Opera, I was pretty disappointed, and even switched to Chrome (because the new Opera is a poor man's Chrome in a way), but after a while I came back to Opera. With that said, Vivaldi looks very promising, but it's still too buggy! I'm holding my fingers crossed.

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

#427

Post by dredmorbius »

jo_ wrote: post #98
mason55 wrote: post #60

Earlier quoted context omitted.

> I keep a lot of tabs open and began to notice Chrome was filling up my memory. I had this problem too and found that Chrome was getting so slow that it was unusable. For those who have this problem and don't want to switch from Chrome there is an extension called "The Great Suspender" which dumps background tabs after a configurable time period of inactivity. It helped immensely.

This looks exceptionally helpful. I have around 50 tabs open, nominally, and my CPU fan is almost perpetually on high for it. Just before installing it, however, I found myself wondering, "Why am I using an app which allows me to keep more tabs open? Why am I not using bookmarks?" Why do we keep open 500 tabs instead of using bookmarks these days?

That's an excellent question, and one I started asking myself about a year ago. My conclusion: it's a lousy band-aid over poor browser document and state management.

https://www.reddit.com/r/dredmorbius/comments/256lxu/tabbed_...

If I had a _better_ way of keeping track of what it is I'm currently accessing (or interested in accessing) than tabs, I'd use them.

A key problem is that browsers are keeping _every last tab fully open and rendered in the fear that you might need to immediately access is_. The tendency of websites toward full interactive designs exacerbates this problem.

Really: most text is pretty static. Generally I'm viewing one page at a time. Perhaps 2-5. The rest ... they can just go off and die.

Having them _saved locally in a state that's suitable for quick re-render_ would be kind of cool. Again, yes, this means that a lot of interactive page shit dies. But then, it should.

IMO webpages should earn their privileges. Including whether or not to animate, or play video, or audio, or display nonrelevant sidebars, headers, footers, and the rest.

The present browser / Web paradigm is grossly overextended and deserves to die.

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

#428

Post by cpeterso »

wldcordeiro wrote: post #210
frik wrote: post #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 c…

If you have Electrolysis there should be more than just firefox and plugin-container. Currently I run Nightly as my main browser and have to keep it disabled though due to some plugins I use lacking Electrolysis support (the fix is not on the plugin maker's side.)

Note that both the Flash sandbox process and the Electrolysis content process are named "plugin-container.exe". If you just see a Firefox and one plugin-container process, it is likely the content process, not Flash.

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

#429

Post by Zancarius »

yellowapple wrote: post #399
Zancarius wrote: post #325

Earlier quoted context omitted.

Edit: I want to apologize to eridal. I misread his/her statement and though the browser in question was Chrome, not Firefox. So, public apolgy: I'm very sorry, eridal. I thought you wrote something you did not. My comment was wrong as a result. I have corrected my mistake, and wish to apologize to you personally for misreading what you wrote. Original message with the offending part removed, mistakenly assuming erida…

I, at least, do typically run with anywhere from 50-200 tabs (or more!) at any given time. Yeah, there's some slowdown if you're running on an 8GB machine (I'm typing this on a Macbook Air with a Firefox session with at least 100 tabs open at the moment (SEE EDIT)), but it's certainly way more than I used to get with Chrome before I switched back to Firefox a couple years back (Tree View Tabs being the motivating fac…

Same here. I'm regularly hitting 200+ tabs on multiple profiles for various reasons (news, documentation, etc.). This is precisely why I use Firefox for all my browsing usage (and have for some time). Chrome/Chromium chokes once you hit about 100-150 tabs, and the tab UI is not usable once open tabs fall off the edge of the window (there's probably an extension to fix this).

Now, I will admit that Firefox misbehaves once you hit about the 500 tab threshold (or higher) to the extent that closing it takes longer. But since tabs aren't loaded on restart until you click them, its memory usage tends to stay much, much lower during regular usage.

I want to like Chrome. It's fast, it's pretty speedy, but for my use case, it's not ideal. It's good for some things, but Firefox is much better behaved!

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

#430

Post by _lce0 »

Zancarius wrote: post #325
_lce0 wrote: post #300

Earlier quoted context omitted.

I've using firefox on a 4Gb linux machine for about two years so far.. and it's working just fine, each release it keeps better and better

Edit: I want to apologize to eridal. I misread his/her statement and though the browser in question was Chrome, not Firefox. So, public apolgy: I'm very sorry, eridal. I thought you wrote something you did not. My comment was wrong as a result. I have corrected my mistake, and wish to apologize to you personally for misreading what you wrote. Original message with the offending part removed, mistakenly assuming erida…

why don't? unused tabs won't consume much, or at least noticeable to me.

I do have a coffee-break whenever I open my IDE

Post reply on HN