Fuck It, I'm Going Back to Firefox • Hacker News Board

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

#361

Post by dblohm7 » Fri, Feb 13, 2015, 9:15 PM UTC

frik wrote: post #215

jsheard wrote: post #157

Earlier quoted context omitted.

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.

Chrome 1+, IE 9+ and Safari 7+ spawn child processes with less permissions ("sandbox") for almost every tab. Sadly Firefox 39 (nightly) still has no real multi process support. There are only two processes, the main process holds all tabs, the single child process "plugin-container" holds all plugins (Flash, Acrobat, etc.). It's a bit disappointing to see such little progress since 2010. Hopefully Mozilla's Rust base…

"Sadly Firefox 39 (nightly) still has no real multi process support. There are only two processes, the main process holds all tabs, the single child process 'plugin-container' holds all plugins (Flash, Acrobat, etc.)."

That is incorrect. There is one plugin-container for each plugin module. All Flash instances share a single plugin-container, all Acrobat instances share a single plugin-container, and so forth.

As for the e10s content process, for the moment there is only one content process. The plan is to get e10s working well with the one content process, and then start scaling that up to multiple content processes. Nightly is a bleeding edge development channel, after all.

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

#362

Post by praetorian84 » Fri, Feb 13, 2015, 9:16 PM UTC

I use both Firefox and Chrome pretty heavily at work. I still prefer the web dev experience in Chrome. The general browsing experience gap has definitely narrowed. Flash + Firefox used to be painful, but I'm not noticing that anymore.

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

#363

Post by dblohm7 » Fri, Feb 13, 2015, 9:17 PM UTC

frik wrote: post #243

pcwalton wrote: post #39

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…

"one child process that holds all plugins (Flash, Acrobat)."

Not true. Each plugin module gets its own plugin container. Flash instances share a separate plugin-container from the one shared by Acrobat instances.

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

#364

Post by ntsh » Fri, Feb 13, 2015, 9:18 PM UTC

soperj wrote: post #336

Slippery_John wrote: post #303

Earlier quoted context omitted.

Tabs were one of the major reasons I switched over to Chrome. At the time, firefox resized the tabs as soon as space became available, making closing a bunch of tabs a pain. They don't do that anymore, but now they have the tab scrolling feature which adds a gui element if there are too many tabs. Thing is, once you close enough tabs, those elements go away immediately, making closing a bunch of tabs a pain. Biggest…

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.

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

#365

Post by osw » Fri, Feb 13, 2015, 9:18 PM UTC

Touche wrote: post #176

bloodorange wrote: post #92

Earlier quoted context omitted.

firefox --new-instance --ProfileManager

Good to know. Only thing remaining would be a way to distinguish between them.

different theme per profile

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

#366

Post by Truespeed » Fri, Feb 13, 2015, 9:18 PM UTC

DontBeADick wrote: post #161

My favorite "feature" of Chrome is the way it invites people to look through your browsing history every time they open a new tab, and there's no way to disable it. There used to be a way to disable it, but they removed it sometime last year. Because users don't know what they want, right Google?

There's the "Blank New Tab" extension: https://chrome.google.com/webstore/detail/pfdloiaebhgmjpaclb...

It's only 1.7 KB

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

#367

Post by AceJohnny2 » Fri, Feb 13, 2015, 9:18 PM UTC

groovylick wrote: post #337

I returned to Firefox from Chrome about 1 year ago due to nagging rendering bugs with linux. Running out of video memory triggered a bug where Chrome would leave a stale buffer of the window on screen. My inputs still got to browser, I could change tabs, scroll, go full-screen it just won't repaint the window. I would have to restart my window manager to get it to repaint. The only solution was to disable GPU renderi…

I have a similar experience, and also switched back to Firefox on Linux. There must be something in my setup [1] that screws with Chrome's expectations, because its performance and stability are horrendous on this computer.

It runs fine and dandy on my Windows machine though.

[1] Ubuntu 12.04, dual-monitor, AwesomeWM, Nvidia Quadro FX 580, 8-core and 8GB RAM,

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

#368

Post by dblohm7 » Fri, Feb 13, 2015, 9:19 PM UTC

joshstrange wrote: post #203

chimeracoder wrote: post #133

Earlier quoted context omitted.

> So still not in stable and Chrome has had it for what? 4 years now? Chrome is a much newer browser. At the time Chrome was released, it was the only browser with this design, because it's much easier to do when starting from scratch. Chrome benefited greatly simply from observing the design decisions of Firefox, IE, etc. that had had several years to play out by that point. In ten years (assuming Chrome is still ar…

IIRC Chrome did not have this feature day 1, they added it after the fact. That's not to say they didn't plan for it but still.... Also "Chrome benefited greatly simply from observing the design decisions of Firefox, IE, " Yes and Firefox benefited from observing the browsers before it, so what? > "In ten years (assuming Chrome is still around then), it will also have similarly antiquated design decisions that make s…

I don't think people are taking issue with the fact that you switched; they're taking issue with your indirect suggestion that Mozilla is taking too long to implement multiprocess.

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

#369

Post by osw » Fri, Feb 13, 2015, 9:19 PM UTC

I use surf for most of things, firefox is one fat panda.

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

#370

Post by seba_dos1 » Fri, Feb 13, 2015, 9:20 PM UTC

Zancarius wrote: post #325

_lce0 wrote: post #300

Earlier quoted context omitted.

I've using firefox on a 4Gb linux machine for about two years so far.. and it's working just fine, each release it keeps better and better

Edit: I want to apologize to eridal. I misread his/her statement and though the browser in question was Chrome, not Firefox. So, public apolgy: I'm very sorry, eridal. I thought you wrote something you did not. My comment was wrong as a result. I have corrected my mistake, and wish to apologize to you personally for misreading what you wrote. Original message with the offending part removed, mistakenly assuming erida…

I don't doubt. Firefox with hundreds of tabs works well with 4GB RAM, and somewhat bearable on 2GB, with occasional restart once per week or so to clean it up.

On the other hand, I wasn't able to use Chrome the same way I use Firefox on PC with 8GB RAM.