Live data from Hacker News

Fuck It, I'm Going Back to Firefox

gizmodo.com

371–380 of 654 posts

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

#371

Earlier quoted context omitted.

This is probably b/c most people at Google use computers with 32GB of ram.

This might sound silly to some, but I wouldn't be surprised if Google limited its usability tests to high-end machines with RAM in the double-digits. I reckon most programming teams have this issue, since even if they're dogfooding, they're doing so on high-end hardware, meaning that low-end hardware is untested and often unusable. Google isn't the only culprit; many websites nowadays will start to lean heavier towar…

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.

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

#373
post #247

Earlier quoted context omitted.

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.)

I run the current Firefox 38 Nightly 64-bit Windows version with "Enable E10S (multi-process)" turned on (default setting). There are only two processes.

That's temporary. Once e10s has been stabilized with one content process, they'll look into scaling that up.

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

#375

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 f…

How about filing a bug for that Sync problem?

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

#376
post #243

Earlier quoted context omitted.

> Finally, it's still not multi-process (though it's finally getting there.) [2] In fact, Nightly now is by default.

You mean one main "firefox" process that holds all tabs and one child process that holds all plugins (Flash, Acrobat). So if one tab hangs (e.g. WebGL demo) then still the whole Firefox is slow as hell. Firefox should finally spawn child processes for every other tab with less permissions ("sandbox" technique) so that if one tab hangs or crashes every other tab and the UI still is responsive. It seems we have to wait…

you can split the tabs over more than one process (by increasing dom.ipc.processCount), but that's even more experimental than e10s itself

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

#377
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…

I still use pentadactyl, even though it isn't being supported AFAIK. These kind of customizations are not possible on chrome. This is why I never switched even when it was cool.

I love Pentadactyl too, that's why I'm amazed it's no longer supported. Seems to me that with all the vim and Firefox-using devs out there, a lot of people would want to support it. But I have no evidence of that.

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

#378
post #310

The only reason I don't use Firefox anymore is because it doesn't automatically pick up changes in my proxy settings, whereas Chrome does. So with Chrome I can have tabs open on my laptop at work, then bring it home and continue to use the same tabs, while with Firefox I have to remember to go in and change my proxy settings.

You could request this by filing a bug in Bugzilla.

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

#379

I'd like to switch back to Firefox, but they do not support inverted colors like Chrome does. Hacker Vision on Chrome is sooooo good. The closest I've found for Firefox is Color Toggle, but it fails in a lot of places, enough that FF+CT is not usable as my main browser. (This difference might be laid at the feet of the plugin writers, but I have the idea that there is inversion support available in the browser in Chr…

File a bug for it. Maybe somebody will implement that for you!

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

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

exactly!! I don't want Google everywhere.That's why I changed the default search engine to duckduckgo. Let's see how it goes.

I tried that. DDG just wasn't even remotely good enough to service my searching habits.

Instead, I've switched to Disconnect search. They proxy searches and claim to do so anonymously. So at least I'm not directly contributing to Google's profile building that way. It does add a second or two latency per search, which can be annoying.

FF switched to Yahoo, and I'm just amused at how bad it is. They even open results in new tabs by default, a lame trick used to try to accidentally keep people on your site.

It's unfortunate, but Google really does dominate in search.

Post reply on HN