"No Multi-Process Architecture" This is a feature, and I like it. The rest is just flamebait.
how is this a feature?
I have more than a 100 tabs open at once, it DOES add up.
Here’s Why Firefox is Still Years Behind Google Chrome
21–30 of 175 posts
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#22Chrome 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.
This is precisely the reason why I still use Firefox. It's impossible to use Chrome on wide gamut displays, everything looks oversaturated. http://cameratico.com/guides/web-browser-color-management-gu...
Chrome now supports ICC profiles for images, but still fail to color manage page elements, which is a deal breaker for me.
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#23Also: Firefox seems to discourage you from messing with cookies. For example: I can't select cookies by TLD. I have to painstakingly go through the list, clicking each host and clicking "Remove". Compare the cooking management functionality with the next tab over, password management. There you can filter the list as you want. So it is possible.
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#24According to Snowden's leaked Prism slides, Google was brought into the NSA fold on the 14th of January 2009. So Firefox is well over 4 years behind Chrome in that respect as well. Get your act together, Mozilla!
Seriously? Can't there be one discussion on here that isn't about Snowden or Prism?
So long at people get karma for lazy low-content references to whatever cause everyone is swept up in they won't stop posting them.
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#25Chrome 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.
> no proper color management in Chrome
Can you elaborate on this? I'm relatively new at it, but I write code for a color science company so I'm curious as to what you mean.
Edit: I'm also reading halfcamerageek's URL: http://cameratico.com/guides/web-browser-color-management-gu...
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#26Well, Chrome can't even be installed without being a pig about it -- no way to set the installation location, no option to disable the background updates or keeping the last few versions of Chrome around. I guess it's okay if you don't really do much with your computer though, and don't mind the resources wasted on Chrome being needy. (e.g. I have old school DSL with 100 kb per second; I like to choose when I want a browser update, and it's hardly hi-tech to allow for that)
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#27Earlier quoted context omitted.
how is this a feature?
Lower memory usage (I think).
You know, because the reason there are threads in the first place is that a single running process can share its global variables and heap space. When Chrome runs in multiple processes, it has to duplicate its global (mostly static) variable space each time.
Albeit, that is certainly peanuts next to the v8 interpreters heap, the web page itself, loaded images, etc, but there is a reason few programs do the multi-process thing.
Chrome doesn't really get a speedup from it, it gets a stability bump. If one tab crashes in Chrome a tab goes, if a tab in firefox goes it drops the whole browser process.
As a development design pattern, if you are concerned with stability, you fork your threads into their own processes and prepare for them to go down in flames.
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#28I will say this for Firefox--the recent work to fix memory leaks has created a HUGE improvement. I often have dozens of browser windows or tabs open for days at a time, since I just sleep my laptop between work sessions. Firefox is now as stable and snappy as any other browser over such time frame. It's really a great improvement.
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#29With all the nice items recently implemented in Chrome and all the lagging behind and alleged slowness of Firefox, I still see "aw, snap! crash!" in Chrome an order of magnitude more frequently on my screen than Firefox crash reports. However the slowness of Firefox when Firebug is on when loading resource-heavy pages starts really bothering me.
Could it be their their Flash implementation? I'm using FlashBlock, and I never experience crashing in Chrome.
Re: Here’s Why Firefox is Still Years Behind Google Chrome
#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://arewefastyet.com/