3 ms·
Second to openssl? I would rank gpg as the worst by a considerable margin. Although, come to think of it, tex and its relatives (pdflatex, etc) have really qu
by amluto 6y ago
Second to openssl? I would rank gpg as the worst by a considerable margin.
Although, come to think of it, tex and its relatives (pdflatex, etc) have really quite terrible command line interfaces.
- R0b0t1 6y agoImporting and managing keys and encrypting messages is something I do via CLI because it is easier to do what I mean, not what some developer thinks I mean. The CLI is more expressive and I don't think to the detriment of usability. It's just for most people, they're not used to working with a tool that merges communication and text processing with a CLI interface.
- axaxs 6y agoI dunno, Openssl CLI is one hairy beast. To be honest I don't really know the best solution to such problems. Smaller, more specialized binaries? I mean, s_client is so vastly different than say, rsa.
- jcranmer 6y agoffmpeg is pretty nasty as well, and I don't have much fondness for ImageMagick's command line either.
- dgellow 6y agoThey are both old and really complex tools, that explains part of it.
- smichel17 6y agoAt least ffmpeg makes it easy to do the very easiest thing. I don't have to look up this one: ffmpeg -i input.file output.file Now, usually I want to do something more complicated, so I end up having to look it up, but it's hardly the ffmpeg folks' fault that audio and video encoding is such an ungodly mess of different containers and encodings; while it could be better, I think most of its complexity is inherent to the problems it's trying to solve. I do think there's an argument that it tries to do too much, and the complexity could be mitigated if it were split into several smaller tools and a wrapper for the most common commands, like apt.
- forty 6y agoAgreed, I'm not sure what's wrong with openssl's cli and git's cli (I do agree gpg's sucks). Those are pretty complex tools that can do many things, so they cannot be expected to be used without learning to use them or reading the manual.
- smichel17 6y agoI think the mantra of "Make simple things easy and hard things possible" applies here. These tools all do a poor job of the former. Now, if you're writing a low-level tool (in git's terminology, plumbing), that doesn't matter as much, because it's designed to be wrapped; maintainability and (interface) stability probably take priority over being maximally intuitive. But if you're writing a tool for end users (including developers), some focus on UX is warranted. (How much each of these tools are intended for end users, can be argued separately, not by me)
- amluto 6y agoExcept that gpg also fails to make the hard things possible. Want to verify a signed file against a key that’s in another file? Nope, not supported. Want to load a private key into a smart card without wiping the key from your keyring? Not supported. In general, gpg has a very strong idea of how you’re supposed to use it, and it makes it very hard to do anything differently.