I think it also helps to think about what the consumer of your tools is, and how often the command-line needs to be written.
Is it a tool like Git, that you run over and over again, many times throughout the day?
Or is it something like 'find', where you run it every once in a while, but aren’t used to using it?
Or is it something like 'ld', where you only ever run it from your build system?
Tools like Git it's nice to have options like -p for --patch.
Tools you only use from build scripts—easy enough to only give them long options. You don't need short options, mostly. Same goes for tools that are only written seldom. You won’t remember what the short options mean, for a tool that you run once or twice a month, so you’re just shooting yourself in the foot by using them.
Is it a tool like Git, that you run over and over again, many times throughout the day?
Or is it something like 'find', where you run it every once in a while, but aren’t used to using it?
Or is it something like 'ld', where you only ever run it from your build system?
Tools like Git it's nice to have options like -p for --patch.
Tools you only use from build scripts—easy enough to only give them long options. You don't need short options, mostly. Same goes for tools that are only written seldom. You won’t remember what the short options mean, for a tool that you run once or twice a month, so you’re just shooting yourself in the foot by using them.