tokei VS cloc

So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%

[0] https://github.com/XAMPPRocky/tokei

[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...

thirdly: found this (https://github.com/XAMPPRocky/tokei) and wanted to analyze languages used on my system, didn't see a package manager (apt) for it that I had. So i installed cargo via apt-get rustup. Added the bin folder to $PATH via PATH=$PATH:~/.cargo/bin. But did not make it permanent. And stupidly rand tokei on "/", realizing how long and unhelpful that would be killed it. Then ran it in a dump folder with some very nested repo dumps, and tons of wolfram.nb files. After killing that too, and attempting to kill via system monitor. Still have two of those as zombie processes.

tokei

For what it's worth, tokei seems to be named after tokei.

BTW, for more info on how it is done, you can check out tokei which is the library use by onefetch for code statistics.

With pytokei you can count code quickly using all the power from tokei, but from python.

Tokei is a nice utility to count lines and stats of code. It is very fast, accurate, and has a nice output. It supports over 150 languages and can output in JSON, YAML, CBOR, and human-readable tables.

Cloc - https://github.com/AlDanial/cloc

and get the results on the cli.

Let me know what you think. :)

0: https://github.com/AlDanial/cloc

Awesome stuff, thank you! I‘d love some flags/options for cloc integration if it can be detected, maybe a summary of the top N languages for directories (67% Rust, 13% Html, 9% Bash) or something. Just a suggestion/idea. Gonna install it anyway, it‘s shiny!

The solution I am using is currently comprised of 145 projects, 141k+ lines of C#, and 37k+ lines of Razor, courtesy of cloc:

Just out of curiosity, I downloaded the latest version of GNU coreutils and compared the line count between a few source files and the resulting disassembled object files (using cloc to exclude blank lines and comments). It looks like the ratio is very approximately 2 assembly instructions per line of C code. Obviously, that will depend a lot on what the code is doing and the coding style.

When I started making a game [0] last year, first thing I did was write a little Unity script that takes a screenshot of the opening scene, counts current lines of code using CLOC [1] (for fun, not as a true measure of anything), and occasionally renders it all out to an image file.

With that I'm able to create some pretty fun time lapses of progress. I've been doing this at an arbitrary milestone, whenever my Luau [2] LOC surpasses C++ by another factor. This post reminded me I'm overdue for another now that Luau > 3x C++ LOC.

I find it rewarding to look back at my progress. I'll share in case it's interesting for you too [3].

[0] https://store.steampowered.com/app/2168330/Helmscape/

[1] https://github.com/AlDanial/cloc

[2] https://luau-lang.org

[3] https://twitter.com/kineticpoet/status/1619508466212831232

My manager just asked me about this a few days ago (sigh) cloc is good for this - you can pass it a hash or two hashes and it will give you counts accordingly. https://github.com/AlDanial/cloc

Finally, since I'm limited on the character-length of this post, I'll post an individual comment for each year with a table of data. The "All Rank" column will rank the problem by difficulty (measured by leaderboard close time) across all years, with 1 being longest. The "Yr Rank" column will be similar, but ranked only within that year. The "P1 LOC" and "P2 LOC" columns show the numbers of lines of code in my solutions for each part as measured by cloc (each part is stand-alone so there will be some duplication, especially for Intcode). Other columns should be self-explanatory.