Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Here’s Why Firefox is Still Years Behind Google Chrome

howtogeek.com

Post reply on HN
Print view View original

81–90 of 175 posts

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#81

Post by bengoodger »

vy8vWJlco wrote: post #36
Gmo wrote: post #6

"No Multi-Process Architecture" This is a feature, and I like it. The rest is just flamebait.

And there is a simple solution to that (poor multi-core utilization): go back to a one-window, one process model (go back, as in delete a lot of unnecessary code); forget the browser tabs - let the OS handle multitasking and let the window manager handle the windows.

This is optimizing for the wrong thing (developer convenience vs. user experience). People like using tabs in their browser more than windows.

This also ignores the other important benefit of mparch: sandboxing. The browser needs some elevated access but the page content does not.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#82

Post by mtgx »

nathanb wrote: post #67

This article is, in my opinion, not very good. It documents areas where Firefox differs from Chrome, yes, but it fails to make the case why I should care. * I don't want a multi-process architecture, I want it so one tab can't kill my entire browser. If Firefox can get there in a different way than Chrome, so much the better. * I don't care whether or not my browser utilizes certain Windows features, since I run Linu…

Why wouldn't you want a multi-process architecture? It's bad enough that so many apps can utilize the quad core CPU's we have in our PC's. At least the browser is one app that can fully take advantage of multiple cores, unlike most apps out there.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#83

Post by jzwinck »

BitMastro wrote: post #20
jzwinck wrote: post #7

Chrome was years behind Firefox, too: https://code.google.com/p/chromium/issues/detail?id=143 - from at least 2008 thorough 2012 there was no proper color management in Chrome, while Firefox had it. This was a deal-breaker for some users. Eventually Chrome copied what Firefox had for many years. It goes both ways.

The first comment on the issue is "It fails in Firefox 3 for me, working in Safari 3 though.", so the feature was copied from Safari?

Back then, you had to enable a preference in Firefox to enable full color management. For people who cared about it a lot, this was more or less OK. The commenter there probably didn't know, and you see people further down mention that. I'm not sure which browser was first to have good color management on Windows, but in any case Firefox had it within a year or so of when wider-gamut monitors started to become popular. Chrome didn't have it for about five years, and during those years I never recommended it to friends because I couldn't use it myself.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#84

Post by freehunter »

Shivetya wrote: post #63
[deleted] wrote: post #50

Earlier quoted context omitted.

[deleted]

Probably the one feature I dislike most about firefox. Having to go to about:config to make changes to my browser behavior. Example, recent install puts tabs on top of address bar. I prefer the old method. Its not a setting I can access through Options, I have to load up about:config, click past the "world is ending" dialog. Then comes the game of guessing what they named this item!

This is better than Chrome's complete lack of configuration. I like my browser to select the entire URL when I click in the URL bar once. On Windows, all browsers do this. On Linux, I don't know of any that do. The difference is, Firefox lets me change that option in about:config whereas the Chrome team blows me off by saying "that's the way native Linux browsers work".

How many Linux users accept "that's the default and you can't change it"?

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#85

Post by Estragon »

SeanDav wrote: post #76
nathanb wrote: post #67

This article is, in my opinion, not very good. It documents areas where Firefox differs from Chrome, yes, but it fails to make the case why I should care. * I don't want a multi-process architecture, I want it so one tab can't kill my entire browser. If Firefox can get there in a different way than Chrome, so much the better. * I don't care whether or not my browser utilizes certain Windows features, since I run Linu…

To this list you can add the deal breaker - Firefox is not mining your data and then passing it on to the NSA.

Even if this were true (and there's no reason to believe that Google Chrome is being used in this way), there's still the open-source Chromium browser.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#86

Post by mrweasel »

SeanDav wrote: post #76
nathanb wrote: post #67

This article is, in my opinion, not very good. It documents areas where Firefox differs from Chrome, yes, but it fails to make the case why I should care. * I don't want a multi-process architecture, I want it so one tab can't kill my entire browser. If Firefox can get there in a different way than Chrome, so much the better. * I don't care whether or not my browser utilizes certain Windows features, since I run Linu…

To this list you can add the deal breaker - Firefox is not mining your data and then passing it on to the NSA.

I would really wish that Firefox provided a way of disabling all external services, including Googles.

If you go to the about:config and search for "Google", I would like the ability to disable all these services.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#87

Post by rcirka »

I use firefox mainly for hierarchical vertical tabs (tree style tab plugin). I often have up to 50 tabs open at once, which is unmanageable in ie/chrome. Also session manager is amazing, never have to worry about losing tabs. I also like how firefox loads tabs on demand, unlike chrome which opens them all when you open the browser.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#89

Post by sp332 »

mtgx wrote: post #77
sp332 wrote: post #4

The first point is odd. I got one of the original Cr-48 Chromebooks, and the current tab would always stutter when other tabs were loading. I installed stock Ubuntu and Firefox on it and I never had that problem. Just lately, in the past year or so, I've noticed the same problem in FF. With all the optimizations they've been making, I can't think what would have changed that behavior.

That's probably just Atom being slow as hell.

Not that I'm disagreeing :) but it happens on my desktop too.

Re: Here’s Why Firefox is Still Years Behind Google Chrome

#90

Post by mixedbit »

tiles wrote: post #30

"If Mozilla can’t turn Firefox into a modern browser because of all the legacy code getting in the way, perhaps we need a Phoenix 2.0." That sounds like Servo [1] to me. That would also be a much more forward-thinking approach to Electrolysis than fully separating the old Mozilla codebase. Firefox is also competing very well with Chrome in JavaScript speed. [2] [1] http://en.wikipedia.org/wiki/Servo [2] http://arewef…

Full rewrite is an ambitious, but very good initiative. Firefox has done (and is still doing) a great service to the web, but its origins can be traced to the Netscape Navigator, one of the very first web browsers. For a huge system like this, it is hard, if not impossible, to change the fundamental architectural decisions, such as a single process model. It is better to take the experience and design a new system from scratch.

I hope Servo can avoid the second system syndrome.

Post reply on HN