122
Linux package names and their consequences
(sh.itjust.works)
Behavior rules:
Posting rules:
NSFW: NSFW content is permitted but it must be tagged and have content warnings. Anything that doesn't adhere to this will be removed. Content warnings should be added like: [penis], [explicit description of sex]. Non-sexualized breasts of any gender are not considered inappropriate and therefore do not need to be blurred/tagged.
If you have any questions, feel free to contact us on our matrix channel or email.
Other 196's:
findis also just a fucking mess in terms of UX. The fact that the ordering of positional and optional arguments are so strongly tied to each other has always driven me fucking bonkers. Nowadays, I installfdeverywhere I can and tell people to switch to it and never look back.locateis nice and all, but I always forget to update the db and I don't want it populating in the background.tardoesn't bug me as much, provided you use unix or GNU style options.tar xvf foo.taris just icky and less readable thantar -xvf foo.tar. I will happily concede that it's not very ergonomic though. I used to rely on things likedtrx(short for Do The Right eXtraction) because it was such a pain to remember the options fortar/unrar/unzip/7z.You reminded me of
fd. Thank you!I got accustomed to the options for
tarand7z. forfind, I just pipe it togrepor uselessto search for something. It just takes time the first time you run itDitto for
tarandunrar, although I deal with.7zso infrequently that I have to look at the manual every time I use it.find's fucked up argument handling really becomes a problem for me when I want to use it in a complex pipeline or when using the-execflag. I've spent far less time debugging in those situations since switching tofd. I won't yuck the yum of folks who are comfortable and likefind, but I feel that we probably have more approachable alternatives for new users.