←back to thread

How I use my terminal

(jyn.dev)
538 points todsacerdoti | 1 comments | 23 Jun 25 15:14 UTC | HN request time: 0s | source
Show context
happytoexplain ◴[23 Jun 25 17:28 UTC] No.44358032[source]▶
The entire blog post being in lowercase distracted me more than I thought it would.
replies(6): >>44358166 #>>44358192 #>>44358472 #>>44358677 #>>44359155 #>>44359809 #
gouggoug ◴[23 Jun 25 17:38 UTC] No.44358166[source]▶
It's also interesting to see that the author themselves are clearly fighting against their own instinct to use uppercase: the first 2 items in the "here's what happens in that video:" list use uppercase.
replies(1): >>44358398 #
jynelson ◴[23 Jun 25 18:03 UTC] No.44358398[source]▶
that's voice-to-text on iOS, i haven't found a way to turn off the auto-caps yet.
replies(1): >>44364872 #
1. latexr ◴[24 Jun 25 11:11 UTC] No.44364872{3}[source]▶
But why are you doing it in the first place? This is a genuine question, what do you gain by actively fighting against proper writing rules which aid in readability and comprehension? What’s the rationale for making it harder for users to follow your post?

I know I’m far from alone in having skipped your post entirely upon opening. Nothing personal, but I have yet to find a single post by anyone written in this style where the content was worth the effort of parsing non-existing capitalisation.

You go through the trouble of adding aids like syntax highlighting, lists, coloured titles, and even differentiated notes and timestamps. Presumably those are there to help the reader. But then you throw away a lot of readability by making everything lowercase.