Live data from Hacker News

Switching from Chrome to Firefox

frunc.de

41–50 of 245 posts

Re: Switching from Chrome to Firefox

#41
post #13

I've always found the Firefox devtools be a little less 'quality of life' like. Just my opinion. Haven't used it in a few years. But for me, I just live in devtools, you know. As most of you here, probably. Opinions?

I always hear people say this, but they never give examples.

The debugger and the source map loading are noticably slower. The DOM browser is slower as well and I get things shifting a few pixels up/down randomly in there.

On the bright side, it keeps a running diff of the css changes you make. Super useful when you're trying to fix some stupid layout thing, get it working and then forget all the changes you made.

Re: Switching from Chrome to Firefox

#42
post #3

Warning for people who use or install Firefox UI Fix on other people's computers: Mozilla occasionally breaks everything with new Firefox releases, and you can end up with a non-functional tabs bar until you reinstall the newest version of Firefox UI Fix. Not so much a problem if you're a techie, but a big problem for the non-techies you install it for.

I don't think it's a good idea in general to install things that utilize unsupported functionality on other people's computers.

Re: Switching from Chrome to Firefox

#43
post #13

I've always found the Firefox devtools be a little less 'quality of life' like. Just my opinion. Haven't used it in a few years. But for me, I just live in devtools, you know. As most of you here, probably. Opinions?

I always hear people say this, but they never give examples.

Fair enough. I just started the latest version and must say, it has really improved. Quality of life probably means I have to look a bit more for where stuff is. And hey, they might have some stuff that Chrome doesn't have, right?

So my first one is 'Chrome devtools has a little button to instantly switch to mobile view, where you simulate (more or less) the viewport of various mobile devices'. I don't see this in Firefox.

Re: Switching from Chrome to Firefox

#44

Earlier quoted context omitted.

> Never had problems with font rendering Okay, so what's the logical conclusion here? That the person is lying? The font rendering is very much off, some people just don't notice or don't care. Denying something others see with their own eyes doesn't help anybody.

As a 15+ years Firefox user: What is "very much off" about Firefox' font rendering? For me it's the opposite, Chrome's rendering looks completely off to me - thin and it looks like the ClearType effect is set to 11. On the other hand, Firefox' font rendering in that screenshot looks like native Windows font rendering to me.

The problem with "very much off" for font rendering is that it is relative to what you are used to, not relative to any actual standard font rendering. If you've been using Firefox a while, Chrome will look off. If you've been using Chrome, Firefox will look off.

Re: Switching from Chrome to Firefox

#46
Something I didn't find mentioning is increasing the number of parallel connections in Firefox. When I inspect the network and responses of FF, I often find connections were "blocked" (for several hundreds ms). Thus, increasing the number of persistent connections to a server will unblock those connections and allow the website to render much faster. Go to about:config and change:

network.http.max-persistent-connections-per-server

from the default value of 6 to 24 or 32.

Experimental results for a website: (time until finish loading)

No of Conns Prime Cache w/o Cache

6 (default) 25 s 257 s

12 21 s 212 s

18 18 s 190 s

24 15 s 147 s

Re: Switching from Chrome to Firefox

#48

I feel this article almost do more harm than good. It paints a picture that you need to "sacrifice" something to use Fx and lists various "problems". For instance it mentions how troublesome it is to use profiles as a "problem". Don't. Use containers. Hundred times more smooth than profiles. Hence why no one cares about making profiles in Fx better, there is already a better solution to the problem profiles solve. Ne…

> I feel this article almost do more harm than good. It paints a picture that you need to "sacrifice" something to use Fx and lists various "problems".

Your comment is roughly of the form “that detailed article lists poor solutions to the problems you’ll likely encounter when switching to Firefox, so please instead follow my detailed instructions about alternate ways to fix the problems you’ll likely encounter when switching to Firefox.” It hardly makes anything feel simpler or more enticing!

Re: Switching from Chrome to Firefox

#49
I wish people would stop mentioning benchmarks, even when Firefox is wins one.

It is like evaluating bicycles based on their towing capacity. Any website that requires a high performance JavaScript implementation is already doing so much wrong that you should just leave.

Re: Switching from Chrome to Firefox

#50

I feel this article almost do more harm than good. It paints a picture that you need to "sacrifice" something to use Fx and lists various "problems". For instance it mentions how troublesome it is to use profiles as a "problem". Don't. Use containers. Hundred times more smooth than profiles. Hence why no one cares about making profiles in Fx better, there is already a better solution to the problem profiles solve. Ne…

> Never had problems with font rendering Okay, so what's the logical conclusion here? That the person is lying? The font rendering is very much off, some people just don't notice or don't care. Denying something others see with their own eyes doesn't help anybody.

They aren't lying, the screenshots are clearly different, but it's strange to describe it as a problem with Firefox. It's a completely subjective difference, to me that Chrome screenshot looks blurry and faint compared to the Firefox one. It's also confusing that they say "fonts are smaller on Firefox" - in those two screenshots the Chrome font is clearly smaller.
Post reply on HN