Slashdot Mirror

← Back to Stories (view on slashdot.org)

How Maintainable Is the Firefox Codebase?

Posted by Unknown on from the self-referential-fox dept.

An anonymous reader writes "A report released this morning looks at the maintainability level of the Firefox codebase through five measures of architectural complexity. It finds that 11% of files in Firefox are highly interconnected, a value that went up significantly following version 3.0 and that making a change to a randomly selected file can, on average, directly impact eight files and indirectly impact over 1,400 files. All the data is made available and the report comes with an interactive Web-based exploratory tool." The complexity exploration tool is pretty neat.

3 of 127 comments (clear)

  1. Does this guy know what Firefox is? by xxxJonBoyxxx · · Score: 4, Funny

    >> A number of modules, namely, accessible, browser and security, frequently appear among the most complex modules. Further investigation may be helpful in identifying why that is the case.

    Does this guy know what Firefox is?

    1. Re:Does this guy know what Firefox is? by Anonymous Coward · · Score: 2, Funny

      A virtual machine running an operating system that by accident happens to have a (rather mediocre) browser? Just like Chrome?

      All that was missing was the relabeling. I guess that's done with "FirefoxOS" and "ChromeOS". ;)

      Now all we need, is to port Linux to it. ... Oh wait!

  2. Re:Lots of pretty numbers... by ArsonSmith · · Score: 3, Funny

    I'm not an expert and of course wouldn't read the TFA but from reading the headline and a good part of the summary, I've deduced that "impact"="bad" and "Indirectly impact"="scary bad".

    Hope that helps.

    --
    Paying taxes to buy civilization is like paying a hooker to buy love.