176- [gocloc](https://github.com/hhatto/gocloc) a sloc counter in Go inspired by tokei
177- [loc](https://github.com/cgag/loc) rust implementation similar to tokei but often faster
178▶- [loccount](https://gitlab.com/esr/loccount) Go implementation written and maintained by ESR
179- [polyglot](https://github.com/vmchale/polyglot) ATS sloc counter
180- [tokei](https://github.com/XAMPPRocky/tokei) fast, accurate and written in rust
· · ·
181- [sloc](https://github.com/flosse/sloc) coffeescript code counter
182▶- [stto](https://github.com/mainak55512/stto) new Go code counter with a focus on performance
183
184Interesting reading about other code counting projects tokei, loc, polyglot and loccount
· · ·
274 Count a specific folder or file:
275 scc myproject/
276▶ scc main.go
277
278 Count several paths at once:
· · ·
365 --no-config disable auto-discovery of the SCC_CONFIG_PATH global and the project ./.sccconfig config
366 -d, --no-duplicates remove duplicate files from stats and output
367▶ --no-fold-authors disable the name+email-domain identity folding fallback for git author reports (mailmap still applied)
368 --no-gen ignore generated files in output (implies --gen)
369 --no-gitignore disables .gitignore file logic
· · ·
601Because some languages don't have loops and instead use recursion they can have a lower complexity count. Does this mean they are less complex? Probably not, but the tool cannot see this because it does not build an AST of the code as it only scans through it.
602
603▶Generally though the complexity there is to help estimate between projects written in the same language, or for finding the most complex file in a project `scc --by-file -s complexity` which can be useful when you are estimating on how hard something is to maintain, or when looking for those files that should probably be refactored.
604
605As for how it works.
+ 19 more matches in this file