Re:The growth of command-line options, 1979-Present
by lalaithion on Tuesday March 03, 2020 @12:22PM
(#22476553)
I feel this way about optional function parameters. They have a tendency to proliferate, because you don't break existing code by adding them, and they're always optional.... until you have https://scikit-learn.org/stable/modules/generated/sklearn.sv..., where you have 15 optional parameters.
[ Parent
| on HN ]
Re:The growth of command-line options, 1979-Present
by blt on Tuesday March 03, 2020 @09:11PM
(#22480636)
None of those SVM parameters stick out as obviously unnecessary to me. What alternative do you propose for functions that have many minor variants with a large common core, and many hyperparameters?
Re:The growth of command-line options, 1979-Present
by dgritsko on Tuesday March 03, 2020 @01:14PM
(#22477140)
Relevant XKCD: https://xkcd.com/1168/
Re:The growth of command-line options, 1979-Present
by chubot on Tuesday March 03, 2020 @04:03PM
(#22478692)
The way I remember tar syntax is to use it more like a "normal" command. That is, instead of the convenient but cryptic idiom:
tar xvf foo.tar.gz # extract, verbose, file
I use the longer but more readable stream idiom: tar -x -z < foo.tar.gz
tar --verbose -x --xz < foo.tar.xz
(It does force you to specify -z for gzip or --xz for .xz, but I'm OK with that redundancy in the name of readability.)This makes it easier to remember the syntax for create and list too:
$ tar --create e.txt k.txt > out.tar
$ tar --list < out.tar
e.txt
k.txt
That's how I write the install instructions for Oil:https://www.oilshell.org/release/0.8.pre2/doc/INSTALL.html
-----
So basically tar can behave normally (at least GNU tar can) -- it's just that there's an ancient idiom that most people have in their fingers, and that's copied around in various instructions.
The nice thing about the verbose way is that the hyphen prefix enables autocomplete.