6 ms·

I wish Mozilla folks woke up. I'm on Mac and, to be honest, once you get used to Chrome, Firefox is completely unusable. It is slow, cluttered interface, w/o a

by maurycy 17y ago

I wish Mozilla folks woke up. I'm on Mac and, to be honest, once you get used to Chrome, Firefox is completely unusable. It is slow, cluttered interface, w/o any major advantages over other browsers. I use Chrome on daily basis and it is pleasure to browse the web. Folks, do not underestimate speed. It is one of the most important UI features.

TNO 17y ago
I wish people paid more attention to developments. #1: Direct2D is in Fx nightlies: http://www.tapper-ware.net/files/stresstest.comparison.ogg http://www.tapper-ware.net/files/stresstest.comparison.ogg #2: Jaeger Monkey: http://www.bailopan.net/blog/?p=683 http://www.bailopan.net/blog/?p=683 #3: 64bit builds are builds are planned for 4.0 if not sooner #4 multi-processes: http://blog.mozilla.com/cjones/2009/06/21/multi-process-firefox-coming-to-an-internets-near-you/ http://blog.mozilla.com/cjones/2009/06/21/multi-process-fire...
varaon 17y ago
Ironically, Flash is the main reason I'm using Chrome. Firefox is plenty fast, but tab isolation means that my browser crashes less often.
- alagu 17y ago
  I'm using vice-versa for the same case. Reason being Chrome takes up 50% cpu on an average when I'm watching youtube videos.
- nollidge 17y ago
  My one nitpick with Flash under Chrome is that for some reason, in fullscreen streaming video (from e.g. Hulu) the mouse cursor never disappears, whereas it does under Firefox.
- Perceval 17y ago
  Out-of-process-plugins are slated for release soon. May not even require bumping the version number to 3.7 – instead we might see it shipped as 3.6.2. Here is the Mozilla project page for separate processes: https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis
rsheridan6 17y ago
I doubt the Mozilla folks can do much about it. It's, like, 7 billion line of C++. How nimble can they be about turning that into a lean, mean, browsing machine? If they haven't done it in 10 years, they probably can't.
- ZeroGravitas 17y ago
  They're actually doing some interesting work in this space: https://developer.mozilla.org/En/Dehydra https://developer.mozilla.org/En/Dehydra Dehydra is a lightweight, scriptable, general purpose static analysis tool capable of application-specific analyses of C++ code. In the simplest sense, Dehydra can be thought of as a semantic grep tool. It presents a wealth of semantic information that can be queried with concise JavaScripts. It is also useful to find bugs in source code as it allows for much more error checking than C++ is capable of by itself. Dehydra is built as a GCC plugin, thus it is easy to use for projects that already support GCC. Dehydra is also useful for generating language bindings and is used to bootstrap Treehydra, a heavy-duty static analysis GCC plugin.
- Perceval 17y ago
  A big cleanup of the code was announced back in 2006: http://weblogs.mozillazine.org/roadmap/archives/2006/10/mozilla_2.html http://weblogs.mozillazine.org/roadmap/archives/2006/10/mozi... They've been working on it since, although I think it has evolved over the past three-and-a-half years. They've got a bunch of automated tools and subprojects to help move things forward.
pohl 17y ago
It might be useful for the FF team to put their tools down for a while and just use Chrome (and/or Safari). Then, upon returning to FF, they might see more clearly what needs to be done to make FF better. Eating your own dogfood is good, but so is thorough study of the competition.
- nollidge 17y ago
  Eat the other guy's dogfood!

by maurycy 17y ago

TNO 17y ago

I wish people paid more attention to developments. #1: Direct2D is in Fx nightlies: http://www.tapper-ware.net/files/stresstest.comparison.ogg http://www.tapper-ware.net/files/stresstest.comparison.ogg #2: Jaeger Monkey: http://www.bailopan.net/blog/?p=683 http://www.bailopan.net/blog/?p=683 #3: 64bit builds are builds are planned for 4.0 if not sooner #4 multi-processes: http://blog.mozilla.com/cjones/2009/06/21/multi-process-firefox-coming-to-an-internets-near-you/ http://blog.mozilla.com/cjones/2009/06/21/multi-process-fire...

varaon 17y ago

Ironically, Flash is the main reason I'm using Chrome. Firefox is plenty fast, but tab isolation means that my browser crashes less often.

alagu 17y ago
I'm using vice-versa for the same case. Reason being Chrome takes up 50% cpu on an average when I'm watching youtube videos.
nollidge 17y ago
My one nitpick with Flash under Chrome is that for some reason, in fullscreen streaming video (from e.g. Hulu) the mouse cursor never disappears, whereas it does under Firefox.
Perceval 17y ago
Out-of-process-plugins are slated for release soon. May not even require bumping the version number to 3.7 – instead we might see it shipped as 3.6.2. Here is the Mozilla project page for separate processes: https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis

rsheridan6 17y ago

I doubt the Mozilla folks can do much about it. It's, like, 7 billion line of C++. How nimble can they be about turning that into a lean, mean, browsing machine? If they haven't done it in 10 years, they probably can't.

ZeroGravitas 17y ago
They're actually doing some interesting work in this space: https://developer.mozilla.org/En/Dehydra https://developer.mozilla.org/En/Dehydra Dehydra is a lightweight, scriptable, general purpose static analysis tool capable of application-specific analyses of C++ code. In the simplest sense, Dehydra can be thought of as a semantic grep tool. It presents a wealth of semantic information that can be queried with concise JavaScripts. It is also useful to find bugs in source code as it allows for much more error checking than C++ is capable of by itself. Dehydra is built as a GCC plugin, thus it is easy to use for projects that already support GCC. Dehydra is also useful for generating language bindings and is used to bootstrap Treehydra, a heavy-duty static analysis GCC plugin.
Perceval 17y ago
A big cleanup of the code was announced back in 2006: http://weblogs.mozillazine.org/roadmap/archives/2006/10/mozilla_2.html http://weblogs.mozillazine.org/roadmap/archives/2006/10/mozi... They've been working on it since, although I think it has evolved over the past three-and-a-half years. They've got a bunch of automated tools and subprojects to help move things forward.

pohl 17y ago

It might be useful for the FF team to put their tools down for a while and just use Chrome (and/or Safari). Then, upon returning to FF, they might see more clearly what needs to be done to make FF better. Eating your own dogfood is good, but so is thorough study of the competition.

nollidge 17y ago
Eat the other guy's dogfood!