I don't know why, but three systems make me google the correct command line options every time I need to use them:
1. OpenSSL
2. Systemd
3. PGP
I have no idea why, but their command line interface is just somehow confusing.
1. OpenSSL
2. Systemd
3. PGP
I have no idea why, but their command line interface is just somehow confusing.
Openssl, PGP and (mentioned in the thread) ffmpeg are often run on one-off basis with changing inputs and outputs and thus almost always require searching the Internet for the correct flags.
If we were using the SQL analogy, I'd say stored procs were closer.
As someone else pointed out, perhaps it's not entirely fair to critic the OpenSSL commandline tool too much, it is in some sense a catch-all reference implementation. On the other hand, Curl have a million options as well, but seems really well put together. Maybe because you only really need a small subset of Curl most of the time, but the same is true for OpenSSL.
If systemctl had something like `systemctl logs -f service`, it would have been much more welcome. Also something like `systemctl start --logs --follow service` would be great.
I'm going to file a ticket for them.
I suspect that its a combination of three things: first, they are not frequently used, second, their CLI is very complex, third, their design violates normal CLI conventions in weird ways.
I don't have the same problem with things like docker or git, which are arguably more complex.
May I ask what git GUI you use? lazygit?
What I do google is ffmpeg, but not before every online editor/converter on the internet completely betrays my expectations and makes me reconsider my life choices.