Quantity Does Not Equal Quality, Firefox 5 Coming Soon
So, the much anticipated Firefox 4 was released just a few weeks ago, and I can’t say the reviews have been too flattering. I downloaded Firefox 4 myself and experienced a crash within the first 24 hours of download. I wanted to give Mozilla the benefit of the doubt, so I checked the mobile version of Firefox 4 on my HTC G2. The reviews were mostly negative. Now I have been a large supporter of Firefox, that is, when I was using a 32-bit operating system. Ever since I switched to 64-bit Windows (necessary to recognize my entire computer memory setup), I’ve had crashes, crashes, and crashes, with Firefox 4 being no improvement.
Of course you can get Mozilla’s 64-bit browser, Namoroka, but being that there is no stable 64-bit Adobe Flash software to accompany the speedy browser, I am stuck using 32-bit browsers. I’ve completely given up on using Firefox upon learning that Firefox 4 was no more stable than its preceding release, and am happily using Google Chrome. Mozilla has reported that they will be releasing Firefox 5 on June 29th. Now, why would they do this? Well, they claim that the new version will add fancy features to tabbing and perhaps deleting the “home” button and replacing it with a permanent tab. The new release is expected to have a “fully customizable menu”, and a few aesthetic changes.
The new Firefox will also have an integrated PDF viewer much like Google Chrome. Now, I think it’s fantastic that Mozilla is releasing an “improved” version of Firefox, but what good are a bunch of extra features if the browser itself is unstable? I can own the most beautiful 1995 Mercedes S-Class, with a fully restored interior but it doesn’t do me much if the engine doesn’t work. What I’m saying is Mozilla needs to work on backwards compatibility for 64-bit operating systems. I realize that 32-bit is meant for 32-bit OS, but the fact of the matter is there is no reliable 64-bit Flash support and we need a browser that can run without spontaneous crashes. Google Chrome got it right, now it’s your turn, Mozilla.