This is a great start :) As mentioned in the post, even people experienced with systems have trouble with it. And thank you for the comment, I've always loved your website (every once in a while, I go and check your "appreciated" page, it's wonderful)
I'm using it for my English101 research paper. Here's what I've got so far. https://kaa.run.place/English101/research.pdf
Yes, that could work. I may spend a paragraph explaining the relative failures of competitors, such as Forth, and Lisp, and APL.
Taketwo: I've got the tools to do that. I'm currently renting a domain from godaddy.com, which provides an API to create sub-domains. I've got a VPS connected to that domain. However, somebody else has already done this project. https://tilde.institute/stats All they're missing is a pretty interface.
New and Improved: the singular dependency, `libhyphen', is included in-tree. The build path is now compiled in to the program without manual intervention. Compiling on Windows is as simple as installing a compiler, a shell, and then running `make win/hyp.exe'.
I went looking for web sites which use `text-align: justify', however the lack of consistent hyphenation seems to have caused aversion from it. Since this is a chicken-and-egg problem, a web page I have written with justification in mind is provided in the `demo' directory, before and after hyphenation.
I happened upon an interview between the Computer History Museum and Chuck Bigelow, partial author of Lucida and the Go fonts. His explanation of the rationale behind the Go fonts was enjoyable to find, and has been excerpted here.
You admit, "[t]his may mean nothing in the grand scheme of things." Computer scientists working in Java, Python, or C# hardly need to care what a syscall is. The Tiobe Index confirms these as 3 of the top 5 most popular general-purpose languages, some 27% of the market.
See https://www.tiobe.com/tiobe-index/.
You make a good point about the paradigm shift from assembly languages -> abstracted languages. But it's definitely interesting to see how this shift affects (admittedly specific instances of) CS curricula. Compilers and computer architecture courses seem to have gone down a similar path, so I wonder how the general CS curriculum will look 5, 10 years from now. Anyways, thank you for the thoughtful reply :-)