Making the best CLI programs - Programming On Unix
Users browsing this thread: 4 Guest(s)
|
|||
(14-09-2016, 02:03 PM)jkl Wrote: Well done after I have posted it in another topic.I crawl the web faster than spiders. ☆*・゜゚・*\(^O^)/*・゜゚・*☆ EDIT: It deals with the programming aspect of the CLI and other stuffs I've completely missed in the talk but that were mentioned in the discussion here. Also, this topic is always recurrent, the usual "no news is good news". Pranomostro mentioned it: (28-05-2016, 10:50 AM)pranomostro Wrote: I heard an interesting idea a while ago, namely that 3 standard files are not enough.And the post author in this section. Obviously, this goes along with the textuality of Unix-like systems, you want to be able to join together the programs and not mess up the output, make it as simple as possible and easy to parse. Here's more: A Guidelines for Command Line Interface Design (or https://clig.dev/ )which discusses in depth the generic view of CLI, the what they are and so what they should do to make it easier, directly leaking from the definition. A typical answer to what a Unix CLI should adhere to. This is the usual boring stuffs but if you haven't gone through it check it out. The unfamous Program design in the UNIX environment which discusses the philosophy and generic design of Unix programs. This is more of a styling guide, an analysis of trends that should be avoided or favored. |
|||