Firefox And The Basics.
Anyone writing programming code makes small mistakes and often those errors go unnoticed for ages, that normally is not a problem with small projects or a quick hack, but it is an issue when that software is released to the public as a viable alternative to Microsoft’s bloatware.
Such is the case of Firefox, the open source adversary of M$’s Internet Explorer.
At one time Firefox even looked like a light weight contender to take IE’s crown, but no longer, recent releases have been comparatively slow and worse still, subject to excessive memory leaks.
Tests showed that Firefox was not the fastest by a long stretch and had stability problems.
I found that out when Firefox 3.0.5 would suddenly consume 98% of processor time and 40% of memory after being left for a few hours with a few tabs open, under several light weight Linux distributions.
That’s not the way it should be. It shows lazy programming and an inability to test to destruction the code. Sloppy.
But there is good news, Firefox seems to be getting its act together the 3.1 beta 2 is great, it uses a lot less memory and has not hung on me yet.
Good job, Firefox, but please try harder.
[…] have found various Gecko based browsers have a bad habit of taking 99% of the CPU, […]
Chrome Of The Brave. « ModernityBlog
16/05/2009 at 02:48