Are Firefox code defects all they are cracked up to be?
I came across the article “Examining defects in the Firefox code base” at g2zero via Slashdot about defects in the Firefox code base. I keep an informal watch on such articles because usually they are sponsored in one way or another by someone opposed to Firefox. I’ll admit that I am a Firefox proponent, but I won’t bash those opposing Firefox.
The author raises some good questions about code specific questions. I am not an expert and many of the issues raised are far more technical than I can understand. However, the question is raised about the defects of the code base. Again I am not a coder, and I don’t understand a lot of the issues.
However, there was a comment posted by Alec Flett that seems to lend some balance to the article. He stated basically that some of the tools used to “detect defects” may actually be working in a vacuum due to the tool not having working knowledge of the code.
So, as with all articles describing defects in software it appears that this one needs to be taken with a grain of caution.
powered by performancing firefox