loc mit Homebrew installieren

Projektlinks

• Homepage

Befehle und Aliase

• loc

Projektgeschichte

The cgag/loc GitHub repository was created in July 2016. The README positions loc directly against cloc and tokei, with old benchmark examples showing loc as much faster on large source trees, while also warning readers that tokei may be smarter or more accurate for some cases.

Adoptionsgeschichte

loc's adoption is concentrated among developers who want a fast one-shot codebase counter and are comfortable with Rust-built CLI tools. Official evidence points to GitHub interest, release binaries, cargo install, and a Homebrew package rather than a large ecosystem of integrations.

Wie es verwendet wird

By default, loc counts the current directory or a target path and prints a language table with files, total lines, blank lines, comments, and code. It is used for quick repository sizing, comparing implementation-language mix, and sanity-checking source tree growth.

Warum Paket-Nerds sich dafür interessieren

loc is significant in the package-manager catalog as part of the Rust rewrite wave of classic Unix developer tools: a narrow utility, fast startup, static-ish binaries, and simple install paths through cargo or Homebrew. Its README also records the healthy package-nerd humility of pointing users at tokei when accuracy matters more than raw speed.

Zeitleiste

• 2016: The cgag/loc repository is created.
• 2018: README note points users to tokei as a smarter and more accurate related Rust counter.
• 2020s: loc remains available through Homebrew and source/release installation paths.

Related projects

• cloc is the older Perl tool that loc explicitly reimplements for speed.
• tokei is the related Rust code-counting tool that loc compares against and recommends checking for accuracy-sensitive work.

Quellen

• https://api.github.com/repos/cgag/loc
• https://github.com/cgag/loc
• source_facts.package-manager