3 ms·
Agreed, 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 ca
by forty 6y ago
Agreed, 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.