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.
exactly!! I don't want Google everywhere.That's why I changed the default search engine to duckduckgo. Let's see how it goes.
Fuck It, I'm Going Back to Firefox
451–460 of 654 posts
Re: Fuck It, I'm Going Back to Firefox
#452The 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 was the driving reason I switched back to Firefox as my main browser about a year ago. It reached a tipping point when I discovered that there was no way to unlink a Google apps business account from Chrome without resetting the browser entirely. Being that I'd never intended to 'sign into Chrome' in the first place (the form looks awfully similar to the gmail login), I essentially rage-quit Chrome and haven't l…
I have multiple g-mail accounts. One of them is my primary personal one, and another one I use is a shared account that my band uses for business and soundcloud.
Google makes it hellish to sign out of one and into the other. For the longest time, I had them linked, and my band mates could see my personal e-mail. I don't know if they could get past a log in point, but the fact that its so hard to keep them un-linked and log into one or the other is infuriating.
Re: Fuck It, I'm Going Back to Firefox
#453using both Firefox an Chrome. Chrome on Linux is very fast and responsive. Firefox on Windows slow and clunky.
Re: Fuck It, I'm Going Back to Firefox
#454Earlier 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.
I found your statement very interesting, and would like to learn more. If you're allowed, would you please provide more details or links to resources that further explain the security issues that process-per-tab resolves?
Here's an old paper that talks about the architecture (it hasn't changed much at a high level):
http://seclab.stanford.edu/websec/chromium/chromium-security...
Re: Fuck It, I'm Going Back to Firefox
#455I don't have to agree with the author's justifications, I switched back some time ago for primary browsing because FireFox makes a browser for me and Google makes a browser for them . Privacy Extensions always seem to work better in FF because it's produced by an organization, if imperfect, whose values center around privacy and not subservience to advertisers. I've worked in offices of companies with ad-supported si…
Re: Fuck It, I'm Going Back to Firefox
#456This article annoyingly misses to mention THE reason to use Firefox over Chrome. Supporting Mozilla.
..plus supporting the open web!!
Re: Fuck It, I'm Going Back to Firefox
#457Firefox also has (experimental) built-in tracking protection without needing to install a third-party extension. The tracking list is based on Disconnect's list. You can activate Firefox's tracking protection by switching the "privacy.trackingprotection.enabled" about:config pref to true.
Re: Fuck It, I'm Going Back to Firefox
#458For me, I like that Firefox isn't constantly bombarding me with "link your accounts" crap. And I like how Firefox still has the option built in to reset the browser / delete all data on close.
Performance seems like a wash these days, and frankly isn't something I care about even a little -- it's basically a problem solved by adding more RAM and RAM is cheap. 16 GB in my laptop these days... 32 GB in my workstation... who cares how it gets used.
Also I like some of the Firefox plugins over Chrome.
I do like how Chrome doesn't require a restart for plugins... Firefox needs to get on that train.
But I add plugins once a week at most, so it's kind of moot.
Anyway I like Firefox more than I like Chrome, that's why I use it.
Re: Fuck It, I'm Going Back to Firefox
#459Earlier quoted context omitted.
Google also happens to be behind the Chromebook effort, so I would be surprised if they don't do any testing on Chromebooks.
Maybe some testing of, say, a few tabs, but I'd be very surprised if a significant number of Chrome devs (or any Chrome devs, for that matter) use Chromebooks for Chrome development ( maybe the Chromebook Pixel, but even that seems unlikely). The Chromebook is optimized toward content consumption; while I'm sure it's possible to do serious programming on ChromeOS (just as it's possible to do serious programming on An…
Many Google engineers (including folks like me outside of Chrome) use Chromebooks as our primary laptops. In my case that also (mostly) makes my Chromebook Pixel my primary computer. I average 25-100 tabs, many of them doing 'heavy' things like editing large Google Docs or running Inbox.
I do have a beefy dev desktop that I access via ssh, although frankly it mostly exists for running emacs for the pedestrian task of actually typing out bits of code.
Re: Fuck It, I'm Going Back to Firefox
#460Earlier quoted context omitted.
We are in the weird situation where even most web application developers run their dev environment on beefier machines than the VMs they are hosting it on.
Great point. I think this is horrible practice and I've seen it lead to lots of slow/clunky code and UX. Next time I start a new team we're all getting Raspberry Pis for development.