Firefox lines of code from tokei. Firefox Lines. This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters. This comment has been minimized. Sign in to view. Copy link Quote reply. Owner Author. Tokei v8.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment. You signed in with another tab or window.
Reload to refresh your session. You signed out in another tab or window. JavaScript HTML C Header More articles by Bastien Abadie…. More articles by Sylvestre Ledru…. Please check your inbox or your spam filter for an email from us. BTW this is also usable for normal webpages Over to LibreOffice we often look to Firefox for inspiration, and we have also built a whole suite of clang plugins that enforce every invariant that we can think of Glad to hear.
I also looked at what LibreOffice is doing and Michael Meeks presentation. Thanks for sharing! Does Mozilla setup some basic rules? Surely not just anyone can change linter rules in the code? Secondly what do you do with payload listing all the potential defects? Does it code through code review or does it go back to the developer who pushed the commit to fix it?
We have many different custom checkers. About the potential defects, we have some heuristic to evaluate if the defects are new or not. If they are, we will show them. Otherwise, we will ignore them.
It would cause way too much noise to show everything old and new defects at review phase. A dot represents one or more dependencies and is read. A module's dependencies are colored distinctly.
A square-shaped cluster indicates the density of dependencies within a module. All the dots to the right and left of a cluster are files that the module depends on.
All files above and below it are files that depend on it. In many paradigms, modularity low coupling, high cohesion is a desirable quality attribute. Hence, an ideal system has modules that have more intra-module dependencies and fewer inter-module dependencies. A matrix can show different types of files, which have varying impacts on quality. Although we calculate the values for these four types of files using the visibility matrix, it is still useful to look for them in a first-order matrix.
Shared files , also known as utility files, are ones that a lot of other files depend on; a shared file that every other file in a codebase depends on would appear as a solid vertical line in an adjacency matrix. Shared files appear to be a positive predictor of quality. Control files , conversely, depend on a high number of files.
Such files appear to be a negative predictor of quality and are hence undesirable in high numbers. They may appear as horizontal lines in an adjacency matrix. Two other types of files are core files , which depend on a lot of files and have a lot of files depend on them, and periphery files , which don't depend on a lot of files and don't have a lot of files depend on them.
These may be a bit more difficult to spot in a matrix. The collective size of clusters can give a partial sense of the number of core files in a codebase. Core files seem to be a negative predictor of quality whereas periphery files seem to be a positive predictor of quality. Evolution of the Firefox Codebase presents a set of metrics for all releases of Firefox that are indicative of quality and allows one to inspect them through one of several views.
By looking at changes in these metrics, one can see the evolution of the Firefox codebase over time. This work is also be useful as a retrospective, investigative tool to help infer when, say, architectural issues may be the cause for unfavorable user sentiment following a release.
Metrics such as lines-of-code LOC and cyclomatic complexity are widely used in industry, whereas others like propagation cost are based on some of the more recent research to come out of academia. Only modules that have a reasonable level of complexity, i. Dexter Dexter 2, 26 26 silver badges 39 39 bronze badges.
Perfect, just what I was looking for. Thanks a lot! I've noticed some Firefox components e. Query: dxr. Some of the things you mentioned live outside of the main mozilla repository.
They are stored in their own github repository, e. Activity Stream lives here — Dexter. Could you maybe point me in the right direction if I wanted to achieve something like this e. Thanks for your help so far, it's very much appreciated. Thanks a lot. I don't think I'm going to be able to achieve what I set out to do, but you've been a great help!
Show 1 more comment. Sign up or log in Sign up using Google. Sign up using Facebook.
0コメント