As does every program that reads from a config file.
One does not have to use files to set the variables of course. This just works well for long-running-programs, e.g. daemons.
"... unless you're putting files in a tmpfs)"
Always files are in mfs.
As for strongly typed data and passing data instead of text, I prefer k to Powershell. There is also a uniformity to APL built-in functions. The number of arguments is limited. PS is quite slow on startup and too verbose.
As for "free-form" sometimes rearranging arguments (as glibc is capable of) can cause more complexity than is warranted.
Consider a program like signify. Then consider gpg.
The best command line program "interfaces" IMO are the ones the fewest options and least possible variability in arguments. Best interface is no interface, etc.
One of the obvious benefits for UNIX programs of this nature is portability.
As does every program that reads from a config file.
One does not have to use files to set the variables of course. This just works well for long-running-programs, e.g. daemons.
"... unless you're putting files in a tmpfs)"
Always files are in mfs.
As for strongly typed data and passing data instead of text, I prefer k to Powershell. There is also a uniformity to APL built-in functions. The number of arguments is limited. PS is quite slow on startup and too verbose.
As for "free-form" sometimes rearranging arguments (as glibc is capable of) can cause more complexity than is warranted.
Consider a program like signify. Then consider gpg.
The best command line program "interfaces" IMO are the ones the fewest options and least possible variability in arguments. Best interface is no interface, etc.
One of the obvious benefits for UNIX programs of this nature is portability.