Fuck It, I'm Going Back to Firefox
601–610 of 654 posts
Re: Fuck It, I'm Going Back to Firefox
#602Earlier quoted context omitted.
As a Chrome developer, I agree that process-per-tab absolutely should not be a replacement for fixing bugs. However, I think it's important to point out that process-per-tab is not just for stability: it's also critical for security.
Chrome is way ahead of Firefox in terms of security. It's worth the performance trade-offs. Each website is rendered in a separate process with a sandbox, each with an empty chroot + process namespace + network namespace + tiny seccomp-bpf + syscall whitelist. Chrome also has a stronger sandbox, pioneers better SSL, supports PIE on binaries, uses pepper - doesnt use native Flash plugins, the JIT compiler does randomi…
Re: Fuck It, I'm Going Back to Firefox
#6031. https://code.google.com/p/chromium/issues/detail?id=143619
Re: Fuck It, I'm Going Back to Firefox
#604I 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.
I used to love Safari but they've lost me with the direction their UI has taken the last few years. There's something about not showing the full URL by default that bugs me.
Re: Fuck It, I'm Going Back to Firefox
#605Earlier quoted context omitted.
I actually have more problems with Firefox's performance than with Chrome's (in terms of processor power), Chrome definitely uses more memory, but it's super fast; firefox is just abysmally slow and can;t handle more than a few tabs. Tried both browsers on Windows 8.1 and Linux, with different machines (home and work computers), too. However, my high memory consumption in Chrome was due to using AdBlock, which is muc…
uBlock is now available on Firefox too, and makes an even more dramatic difference in performance. I really don't know what you're talking about - Chrome is a dog after ~10 tabs are opened, uses crazy memory and becomes unusable fast once it starts paging. Firefox remains stable, backgrounds tabs you're not using in a graceful way, and doesn't try to open and render every single tab at once on a session restore. It's…
Re: Fuck It, I'm Going Back to Firefox
#606Earlier 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…
Re: Fuck It, I'm Going Back to Firefox
#607Re: Fuck It, I'm Going Back to Firefox
#608I pick Safari because now it's fast, memory and _battery_ efficient (I think it's the most battery efficient browser that I've used on the Mac). Apple seems very wary about defending it's users privacy, and it's actually in their best business interests to do so. They have the money and weight to actually put a decent fight on the subject.
That's why I use Safari.
PS: I do use Thunderbird for my e-mail needs though ;)
Re: Fuck It, I'm Going Back to Firefox
#609Earlier quoted context omitted.
My solution to this was to use both. I use Chrome only for Gmail and Docs (drive, whatever...) and disabled the auto-updater. I use Firefox with DDG for everything else. Couldn't be happier.
why did you disable the auto-updater? sounds like a bad idea to stop getting security updates and the like, right?
Speaking for myself, I always disable (i.e. "rm -rf") auto-updaters because they don't separate security updates from other random changes. Browsers are the worst, with a "major version upgrade" every month dropping whatever the developers had on their build server onto my computer.
Re: Fuck It, I'm Going Back to Firefox
#610Earlier quoted context omitted.
Ctrl-w kills a tab. Makes that kind of thing completely painless.
Sometimes Ctrl+w can lead to horrible pain if you accidentally hit Q which is just next to w.