I tend to keep 15+ tabs open at any given time and I can't remember the last time Chrome crashed on me. Chrome's extension ecosystem is better too.
Fuck It, I'm Going Back to Firefox
151–160 of 654 posts
Re: Fuck It, I'm Going Back to Firefox
#152I love firefox, mostly because of the pentadactyl extension(not compatible with firefox 35, sadly) but it has a huge number of problems. Namely, it crashes far too often. It's extremely frustrating, and no number of bug reports I fill out or new releases ever seems to address the problem. I'm thinking of trying to find a better productivity extension, or go back to emacs type shortcuts with chrome or safari. Of cours…
This doesn't help with your main issues, but I think the Vimperator extension is a little better maintained than the Pentadactyl one.
Re: Fuck It, I'm Going Back to Firefox
#153I 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…
He mentioned importing all of his plugins and preferences from Chrome back into Firefox, so it stands to reason that his benchmark between the two is roughly the same. As for the question of will it change? Well, to be frank, it shouldn't. It's known, however, that it will: Chrome in particular is known to not handle the accumulated history well. I haven't had a similar experience with Firefox, but that's only one da…
plugins / extensions are not imported between chrome and firefox, which is the bulk that is being referred to.
Re: Fuck It, I'm Going Back to Firefox
#154Wait, has gizmodo turned into a blog lately? I mean, that's not journalism, that's a rant supported by no benchmarking or any evidence of sort...and while i do agree on the message, i believe that anyone who wants to be called journalist should at least write like one.
Re: Fuck It, I'm Going Back to Firefox
#155I 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.
> 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 little experience in writing desktop applications & memory management in an environment of this nature. Genuinely curious what the normal practice is.
Edit: To clarify, I am assuming the memory growth is not due to any sort of leaks :)
Re: Fuck It, I'm Going Back to Firefox
#156Earlier quoted context omitted.
> Finally, it's still not multi-process (though it's finally getting there.) [2] In fact, Nightly now is by default.
So still not in stable and Chrome has had it for what? 4 years now? EDIT: Ok, downvote me all you want but it's a fact, not opinion. I'd give FF another shot once it's in stable but as it is now I'm not going to waste my time playing on a nightly build.
I don't remember hearing any complaint back when Chrome was all beta and experimental.
Re: Fuck It, I'm Going Back to Firefox
#157Earlier quoted context omitted.
Plus Firefox crashing is a huge downside. How do you get Firefox to crash? What does about:crashes say? Did you report the bug?
Running many WebGL demos. Whereas in Chrome only 1 tab will freeze. Also, pretty much anything that's Javascript + WebGL runs like shit in Firefox. Emscripten demos are good though. But Emscripten runs better in Chrome than JS+WebGL in Firefox.
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.
Re: Fuck It, I'm Going Back to Firefox
#158I 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?
It's not cross-platform.
Re: Fuck It, I'm Going Back to Firefox
#159Earlier quoted context omitted.
Right. That paragraph about the extensions makes me question the credibility of his claims. Disappointing. I haven't experienced the performance problems he describes, and I use the Chrome dev channel for my main browser. I've noticed Firefox has been getting faster over the last couple years, but when I use it I still get the feeling that it gets in my way more than Chrome does. Edit: fix typo
He's part of the rule that tech writers aren't technical people and often write about things they don't understand. As some famous person recently said, there's a huge amount of "intellectual dishonesty" in tech journalism.
To spin it more positively, he and his ilk more generally represent our users than more "in the know" tech-journalists.
I think this is a rough article, but likely one that either many users will empathize with, so the overarching idea that browsers should be doing something to prevent bloat is probably a sound one.
Re: Fuck It, I'm Going Back to Firefox
#160Something 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.
My experience with relatives' computers has been that trying to completely remove Chrome from Windows is a lot like trying to remove a rootkit, specifically one that phones home a lot. If any other company did those sorts of things in persisting pieces of their software all over the OS without easy removal for non-technical users, people would be calling it malware or spyware.
Interesting, what specifically are you having trouble with?
I would think it just uninstalls. Are you claiming otherwise? I'd love to try and reproduce what your claims are (fact check).