If you'd like to collect similar stats for your own code base, check out parker[1] and stylestats[2]. At my company, we aggregate certain numbers from both tools and send them to Graphite to monitor over time, as inspired by this talk from GitHub[3][4].
It almost seems like an on boarding tool for 3rd party CSS but you can't construct or derive style rules from any of the presented formats, just raw colors/sizes.
Because CSS rules are applied by specificity (http://specificity.keegan.st/) first and source order second, any property overwrites later in the document require equal or greater specificity than rules in the middle. A chart with a mountain in the middle today will probably develop more mountains on the right over time - it's a leading indicator of poor maintainability. Pairing this tool with one that tells you the line number of offenders would help in identifying areas in need of refactor.
Total vs Unique declarations reveals opportunities for reusable OOCSS-type classes (which itself can be difficult to do in a stylesheet full of specificity mountains).
The colors aren't terribly useful without a histogram and some of the other stats do seem a bit superfluous, but they may just need someone more experienced than I to draw the right conclusions.
[+] [-] mxpxrocks10|11 years ago|reply
[+] [-] sorahn|11 years ago|reply
[+] [-] peterjmag|11 years ago|reply
[1] https://github.com/katiefenn/parker
[2] https://github.com/t32k/stylestats
[3] https://speakerdeck.com/bleikamp/sass-at-github?slide=68
[4] https://vimeo.com/86700007
[+] [-] shdon|11 years ago|reply
[+] [-] sorahn|11 years ago|reply
I found their github[1] and ran it locally. Worked perfectly.
[1]https://github.com/mrmrs/cssstats
[+] [-] mrmrs|11 years ago|reply
[+] [-] tellor|11 years ago|reply
[+] [-] benologist|11 years ago|reply
It almost seems like an on boarding tool for 3rd party CSS but you can't construct or derive style rules from any of the presented formats, just raw colors/sizes.
The charts and metrics all seem superfluous.
[+] [-] harlanlewis|11 years ago|reply
Because CSS rules are applied by specificity (http://specificity.keegan.st/) first and source order second, any property overwrites later in the document require equal or greater specificity than rules in the middle. A chart with a mountain in the middle today will probably develop more mountains on the right over time - it's a leading indicator of poor maintainability. Pairing this tool with one that tells you the line number of offenders would help in identifying areas in need of refactor.
Total vs Unique declarations reveals opportunities for reusable OOCSS-type classes (which itself can be difficult to do in a stylesheet full of specificity mountains).
The colors aren't terribly useful without a histogram and some of the other stats do seem a bit superfluous, but they may just need someone more experienced than I to draw the right conclusions.
[+] [-] natmaster|11 years ago|reply
[+] [-] mrmrs|11 years ago|reply
http://github.com/mrmrs/cssstats/issues
Thanks!
[+] [-] CoachRufus87|11 years ago|reply
[+] [-] mrmrs|11 years ago|reply
[+] [-] javajosh|11 years ago|reply
[+] [-] zhng|11 years ago|reply
http://cssstats.com/stats?url=http%3A%2F%2Ffacebook.com&name...
[+] [-] _mikz|11 years ago|reply
[+] [-] ww520|11 years ago|reply
[+] [-] elwell|11 years ago|reply
[+] [-] mrmrs|11 years ago|reply