"Are extension design & memory leak fixed yet??"3.5 starson by FL_Guy
Pros: Much better features than IE
Cons: Bugs and design flaws that should never have been released taking a REALLY long time to get fixed.
Summary: IMHO FF is a great browser, significantly advancing the design of web browsers after MS dropped the ball.
However, the time it has taken to address a couple of pretty significant design flaws has been holding back further adoption.
Alow me to submit a couple of examples:
1) It's simply ridculous that all extensions break when a new release comes out.
Yes, I have heard the FF team partly line that it's the extension developer's fault. I don't buy it - imho, it's a poor design (and convention/practice) that breaks existing extensions by default unless/until the extension developers update the compatible version info.
It takes user's time and trouble to install/update extensions. Having to re-do this on every release is a waste of time better spent on more productive activities.
If nothing else, STRONG guidelines to extension developers are needed that extensions should NOT expire until a MAJOR release (and I don't mean one such as 2.0).
2) Memory usage of several hundred MB for a few open tabs is also absurd. As the FF team maintains, this may be the result of a java or other plug in bug, however IF that is the case, they need to find another implementation and stop blamming users, plug-in developers, extension developers and everyone else. This problem really needed to be fixed about 18 months ago.
It would be REALLY helpful if CNET reviewers would address whether any of these issues has been fixed when reviewing a new release.