Firefox 2.0 is not ready for public consumption
Computers October 23rd, 2006
On the heels of Matt Cutt’s review of the Firefox release candidate 2 I decided to give it whirl. I installed the soon to be version 2.0 on my Mac and have experienced many spinning beach ball of death while browsing. The browser locks up on everyday sites and I no option but to kill the process. I guess Matt isn’t on a Mac as he reports no crashes so my advice to the Mac users is to wait for the official release. I also didn’t see much improvement. I don’t really know if I like the fact that it implements SessionSaver by default. Isn’t that a memory hog? On the other hand Firefox doesn’t appear to be using near as much memory as before.
October 24th, 2006 at 1:44 pm
Actually, Firefox still uses the same amount of memory, if not more, as 1.5. There are many complaints about the developers not fixing “firefox-memory-hog”.
January 24th, 2007 at 3:33 am
I just recently set my AIM available message to be “I hate the beach ball of death!” Several people (Mac users, mind you) asked me what the “beach ball of death” was. It makes me feel like it would be a great band name.
(not that any of this has anything to do with Firefox 2.0)