4 ms·
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
by 1vuio0pswjnm7 5y ago
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 trying to show off their programming skills with some new language they are trying to learn, e.g., Go or Rust. Comparing these new programs to original UNIX utilities, many (most) of the UNIX ones seem comparatively simpler.
I write quick and dirty single-purpose utilities for myself because I want relatively simple programs. I try to keep program size reasonably small so I use C not Go or Rust. I avoid creating options. FWIW, seems like that was true of most of djb's utilties, too. Some of the best "new" UNIX utilities I have seen have come from from people who use djb's C functions and/or copy his programming style, including the preference for small program size and few-to-no options. For example, the authors of runit or s6 have some interesting utilities. The author of tinysshd has some useful ones as well. These projects are generally not popular but they are generally high quality, IMHO.
There are some JSON utilities listed on this blog page. Despite so many options for libraries and programs to process JSON, I still cannot find one that does something very simple: 1. extract JSON from HTML, 2. print it in a customised, human-readable, left-justified format that 3. makes it easy to process further with other programs. Hence I wrote a stupid program for myself that extracts JSON, prints the keys and values left-justified, making it easy for me to read with less(1) and to process with traditional UNIX text-processing utilities. (I am probably mistaken but I believe the one I wrote may be able to operate at the same speed regardless of the size of the JSON data. This needs to be tested.)
I have written several shell scripts over the years that have a subset of the functionality of fzf (or a superset of urlview's, which came much earlier), namely finding and selecting items from lists. I am still not a fzf convert because generally it does not do anything essential I cannot already do myself. Plus it is larger, more complex and generally slower.
Someone once said the best interface is no interface. For me, the less required user-interaction (including selecting options), the more powerful the utility.
- forgotpwd16 5y ago>consitently too complicated, e.g., too many options At least one of them (fd) was designed specifically to be simpler to use than its UNIX counterpart (find). And others though as simple to use (ripgrep, scc) they're much more performant than the tools they replace (ack, cloc).
- b5n 5y ago> Perfection is achieved, not when there is nothing more to add, but when there is nothing left to take away.
- marttt 5y ago> 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.com/journal/2012/08/the-best-interface-is-no-interface.html/ https://web.archive.org/web/20120831083217/http://www.cooper... Previous HN discussions: https://news.ycombinator.com/item?id=4616945 https://news.ycombinator.com/item?id=4616945 (2012, 87 comments) https://news.ycombinator.com/item?id=4454004 https://news.ycombinator.com/item?id=4454004 (2012, 34 comments) https://news.ycombinator.com/item?id=4959406 https://news.ycombinator.com/item?id=4959406 (2012, 91 comments) https://news.ycombinator.com/item?id=9218686 https://news.ycombinator.com/item?id=9218686 (2015, 56 comments, about the book) EDIT: One of the old comments also addressed Unix tools more directly, referring to djb's work: https://news.ycombinator.com/item?id=4456795 https://news.ycombinator.com/item?id=4456795 What are some relevant writings by djb on user interfaces?
- 1vuio0pswjnm7 5y agoThe article on The Verge looks like it's about mobile phones, i.e., pocket-sized computers meant to be operated with touchscreens. Granted, today we can plug tactile USB keyboards into some of these "phones" and we have options like Termux, but the subject here, unlike the The Verge article, is command line programs. 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