the repo is here btw. i appreciate that the dependency tree is appropriately minimal. also impressive how many comments are included in the source. maybe they’re not counted towards the LOC?
Even though that's 400-ish over, the readme states:
1.: Counted per platform, excluding tests and Clippy directives, see count_loc.sh
However, I personally feel like it's a stupid metric anyway because that doesn't count dependencies (although kibi specifically seems to have minimal dependencies), and at some point you could simply abstract your code away into a library and use it as a dependency to prune some lines from the codebase.
It also excludes tests, which is how they reach such a low number. It seems they are trying to count the number of lines actually used in the executable. I can't see the value in this metric. If they want to talk about executable size, they should just use that. If they want to talk about the complexity of maintaining their project, then surely you must count all lines because those still make the project harder to maintain. I guess they're trying to measure the logical complexity of the final result, but I can't for the life of me think why a user or developer would care about this.
the repo is here btw. i appreciate that the dependency tree is appropriately minimal. also impressive how many comments are included in the source. maybe they’re not counted towards the LOC?
reply