Slashdot Mirror
Nine Reasons To Skip Firefox 2.0
grandgator writes, "Hyped by a good deal of fanfare, outfitted with some new features, and now available for download, Firefox 2.0 has already passed 2 million downloads in less than 24 hours. However, a growing number of users are reporting bugs, widening memory leaks, unexpected instability, poor compatibility, and an overall experience that is inferior to that offered by prior versions of the browser. Expanding on these ideas, this list compiles nine reasons why it might be a good idea to stick with 1.5 until the debut of 3.0, skipping the "poorly badged" 2.0 release completely." OK, maybe it's 10 reasons. An anonymous reader writes, "SecurityFocus reports an unpatched highly critical vulnerability in Firefox 2.0. This defect has been known since June 2006 but no patch has yet been made available. The developers claimed to have fixed the problem in 1.5.0.5 according to Secunia, but the problem still exists in 2.0 according to SecurityFocus (and I have witnessed the crash personally). If security is the main reason users should switch to Firefox, how do we explain known vulnerabilities remaining unpatched across major releases?"
Update: 10/30 12:57 GMT by KD : Jesse Ruderman wrote in with this correction. "The article claims that Firefox 2 shipped with a known security hole This is incorrect; the hole is fixed in both Firefox 1.5.0.7 and Firefox 2. The source of the confusion is that the original version of this report demonstrated two crash bugs, one of which was a security hole and the other of which was just a too-much-recursion crash. The security hole has been fixed but we're still trying to figure out the best way to fix the too-much-recursion crash. The report has been updated to clear up the confusion."
Update: 10/30 12:57 GMT by KD : Jesse Ruderman wrote in with this correction. "The article claims that Firefox 2 shipped with a known security hole This is incorrect; the hole is fixed in both Firefox 1.5.0.7 and Firefox 2. The source of the confusion is that the original version of this report demonstrated two crash bugs, one of which was a security hole and the other of which was just a too-much-recursion crash. The security hole has been fixed but we're still trying to figure out the best way to fix the too-much-recursion crash. The report has been updated to clear up the confusion."
A pity as Firefox 2.0 just crashed on me. I was wondering what the hell was going on and I just refreshed slashdot to see this very story.
:(
I still trust it more than IE of course, but do wish as we get newer versions that the stability does continue to improve.
I'm sure they can do it and I still have faith.
Friends don't let Friends use Internet Explorer.
no wonder IE7 team sent a cake to Mozilla foundation a la "from Redmond with love"... See it here if you have not already: http://fredericiana.com/2006/10/24/from-redmond-wi th-love/
The well known memory leak issue, which causes the Firefox browser to consume ever increasing amounts of RAM, eventually leading to sluggish performance and crashes, has been carried over into yet another generation.
So, does that mean that 640K won't be enough memory then?
I love it! Can I have some of that Remond cake?
This is a dealbreaker for me - back to Firefox 2.5.0.7.
you'll need 1.21 Jiggawatts!!1 for that.
Stop Computers/Cars Analogies on S
Welcome to Slashdot.