I think it’s two reasons - first is that human readable formats are less specific, so three files that are “3gb” in size look the same, so it may be hiding information that it knows about
The second is that commands are very often used as parts of larger scripts, where human readability may not matter as much, or may not be applicable until the very last command when the output is actually shown.
Between these, and the fact that most commands try not to predict what your use case is, I think that having a -h option is going to be the norm going forward as well rather than having it as the default
I guess because most of the time the data is consumed by another script. I don’t know how OpenBSD behaves, but I would be pretty angry if I had to put such flags (like “-not-human”) everywhere in my code, docker scripts, and pipelines.
I have the totally opposite opinion, since script writing is where I have a proper text editor with templates and snippets and other helpful tools. Its interactive commands at the terminal that I want to behave as much “human” as possible so I don’t have to type so much
Additionally, OpenBSD leaks the state of the pseudorandom number generator to predictable locations on disk and in system memory at a fixed point during every start up and shutdown procedure.
openbsd
Hot
This magazine is from a federated server and may be incomplete. Browse more on the original instance.