Live data from Hacker News

Fuck It, I'm Going Back to Firefox

gizmodo.com

71–80 of 654 posts

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

#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 absolutely useless on both accounts. What did they say about 'if it isn't broke ...'?

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

#73
post #16

I 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'…

I'm having high hopes for Vivaldi. Chromium with less bloatware but with real Operawesomeness.

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

#74

I find Chrome's web dev tools to be vastly superior to FF and last time I tried it it didn't look good on my Mac and I had the same memory problems as with Chrome. Until FF get's much faster or better devtools than chrome I'm not interested. Not to mention how often does a Chrome extension hit the front page of HN vs a FF one? Don't get me wrong, I don't love Chrome unconditionally (the RAM usage is crazy but so is F…

I heard a rumor a while back that Firefox was developing a browser targeted at web developers. Not sure if thats unnecessary or what but if it materializes I'll probably give it a try.

Yeah, I remember getting excited when I read about that. I'll give it a shot when it comes out but there are a number of little things that annoy me with FF web dev tools that I doubt they will fix. Also I really need to dev on the SAME browser the product will be released on and not some special dev build.

Edit: Oh now I remember why I wrote off:

> Firefox Developer Edition replaces the Aurora channel in the Firefox Release Process.

> By using the Developer Edition, you gain access to tools and platform features at least 12 weeks before they reach the main Firefox release channel.

They just fucking renamed their alpha channel to "Firefox Developer Edition"....

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

#75
was using firefox for the longest while... then as the OP suggests, I switched to Chrome because it was allegedly fast/nimble...

Just downloaded latest firefox - it appears just as snappy (OS X, Yosemite). Don't remember what Chrome used up, Firefox is sitting pretty at 320+ MB memeory footprint with only a few tabs open.

Personally, the whole reason for going to Firefox is my anticipation of their Servo/Rust inspired new browser, which has been in the back of my mind since I heard of Rust awhile back. Can't wait to see how that beasts performs when it's 1.0.

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

#76
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.

I'm honestly curious about the scenario where not having a linked ID caused you data loss. I was an early adopter of Chrome but have not used it for a while. Is this linked ID just the Cookie or another mechanism? How could not having it cause data loss?

Not sure how, but this happened to me. Specifically, my bookmarks accumulated over years seem to have been wiped out when I did decide to sign in. Turns out I had already synced a new computer, so Chrome decided to helpfully delete my un-signed-in bookmarks with the blank set from the new computer.

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

#77

I find Chrome's web dev tools to be vastly superior to FF and last time I tried it it didn't look good on my Mac and I had the same memory problems as with Chrome. Until FF get's much faster or better devtools than chrome I'm not interested. Not to mention how often does a Chrome extension hit the front page of HN vs a FF one? Don't get me wrong, I don't love Chrome unconditionally (the RAM usage is crazy but so is F…

I've found FF dev tools to have everything I need -- it's gotten really good recently. The only thing it doesn't have that I need to switch to Chrome for is for web socket purposes. Chrome allows you to see all the data sent/received in the Network tab.

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

#78
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.

I ditched Chrome for FF a couple of months ago for EXACTLY this reason. The omnipresent account name in the title bar was the clincher.

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

#79
I really like Firefox but the big annoying part that I run into is that Sync seems to blow away extension-specific settings whenever I install Firefox on a new machine. Like, the new machine doesn't have any of my settings for the extensions it knows I already have installed on a different machine, and then Sync happily syncs the new settings to the other machines, blowing it away there too. Thanks, Sync.

I'm a big fan of NoScript and RequestPolicy, but having to "redo" all the whitelisting is a major PITA.

Does anybody else run into this? Am I missing a setting or is there a file I can manually sync (or just backup and restore) to ensure I don't need to endure this pain again?

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

#80

I finally gave Chrome the heave-ho when a recent update forced you to browse under a personal profile. There was a bug in the implementation that would crash the browser if you deleted the profile it created for you (I just wanted to use it normally like I always did!) I ended up inadvertently deleting all my saved bookmarks from the Chrome cloud or whatever. Fed up, I switched to Firefox and have been remarkably hap…

You had always had a profile.. Chrome just made it more visible so that you knew about Guest mode and stuff..

Of course deleting your user profile deleted all of that profile's data

Post reply on HN