None of the "replacements" interest me. When I try the "new" ones I cannot get interested in them either. When trying new programs I am looking for whether a program can do something essential that I cannot do myself, e.g., with shell scripts. However I am beginning to think another reason is that these "new" utilities are consitently too complicated, e.g., too many options. It often seems as if the authors are tryin…
> Someone once said the best interface is no interface. Was this from an article by Golden Krishna, later turned into a book by the same title? Archived article (or, how to open your car door in 13 steps): https://web.archive.org/web/20120831083217/http://www.cooper... Previous HN discussions: https://news.ycombinator.com/item?id=4616945 (2012, 87 comments) https://news.ycombinator.com/item?id=4454004 (2012, 34 comme…
Maybe no one besides me ever actually said those exact words with respect to command line programs. What did happen is someone wrote that he found user interfaces on command line programs are not "good" interfaces. He then suggested that writing command line programs that did not have to parse options could be a "security" tactic when programming. See "5. Don't parse" in the text file below.
tnftp -4o"|tar xOz qmail-1.03/SECURITY|less" https://cr.yp.to/software/qmail-1.03.tar.gz