C
Curtis McEnroe
cmcenroe.me · Personal blog · on HN since 2014
Curtis McEnroe writes about low-level programming, including the Linux framebuffer, x86 assembly, Rust, and minimal web styling.
What HN saysCommenters link it as a nice quick tutorial on the Linux framebuffer and for the Writ stylesheet, though one reports a scrollbar bug in its reference page.
15HN people shared it
3linked it in comments
14stories submitted
723story points
2 years agolast shared
2014people per year2026
Most-shared posts
- 1Programming the Linux Framebuffer4 people · 176 points · first shared 2018 · 24 comments on HN
- 2A Formula for the Number of Days in Each Month1 people · 222 points · first shared 2014 · 106 comments on HN
- 3Writ – Opinionated, classless styles for semantic HTML1 people · 150 points · first shared 2015 · 61 comments on HN
- 4Building a Tetris Clone in X86 Assembly, Pt. Ⅰ: Hello, World1 people · 71 points · first shared 2015 · 13 comments on HN
- 5Building a Tetris Clone in x86 Assembly, pt. Ⅱ: I/O1 people · 59 points · first shared 2015 · 10 comments on HN
- 6ASCII to My Heart1 people · 27 points · first shared 2015 · 1 comments on HN
- 7Why Rust Appeals to Me1 people · 14 points · first shared 2015 · discussion on HN
- 8Chromebook as a Thin Client for Development1 people · 2 points · first shared 2015 · 1 comments on HN
- 9I made my own colour scheme and you can too1 people · 1 points · first shared 2018 · discussion on HN
- 10System V ABI Quick Reference1 people · 1 points · first shared 2017 · discussion on HN
- 11Reference1 people · first shared 2015
- 12Uloc1 people · first shared 2024
What HN people wrote when they linked it
Koshkin · 2020-06-15
Here is a nice quick tutorial on using the frame buffer in Linux: https://cmcenroe.me/2018/01/30/fbclock.html
red_admiral · 2015-08-25
On the reference page https://cmcenroe.me/writ/reference.html the aside note causes a horizontal scrollbar for me. Chromium 43.0.2357.81 (64-bit) on linux.
boyter · 2024-07-29
More lines of code usually indicates more bugs so its not an entirely useless metric. Using it to gauge employee productivity is, since as the linked suggests some of the better programmers are able to remove code, which often reduces the potential for bugs.
I personally find some use it in, if nothing else to identify which files probably need to be refactored as they are too large, or complex. Throw in some cyclomatic complexity and you are getting some useful information out the code counts.
Counting lines of code is one metric though. Another I have seen thrown around is ULOC https://cmcenroe.me/2018/12/14/uloc.html where you count the number of unique lines of code,
sort -u *.h *.c | wc -l Again another metric that potentially speaks to the health of a project. I personally wrote about this some time ago when someone asked why I wrote a code counting project https://boyter.org/posts/why-count-lines-of-code/ and I liked the idea of ULOC so much I integrated it into the project as well.
Clearly I am not alone in this though, hence there being so many code counters around (forgive me if I missed yours in the following list) and discussion around it.
- [SLOCCount](https://www.dwheeler.com/sloccount/) the original sloc counter - [cloc](https://github.com/AlDanial/cloc), inspired by SLOCCount; implemented in Perl for portability - [gocloc](https://github.com/hhatto/gocloc) a sloc counter in Go inspired by tokei - [loc](https://github.com/cgag/loc)…