Linux package names and their consequences

196@lemmy.blahaj.zone – 107 points – 2 days ago

! A screenshot of a Linux terminal showing some packages being installed. One of the package is named "fribidi". This name rhymes with something that evokes visceral horrors beyond comprehension.
An image of a Vietnam war soldier having flashbacks is superimposed !<

You are viewing a single comment

View all comments Show the parent comment

find is 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 install fd everywhere I can and tell people to switch to it and never look back. locate is nice and all, but I always forget to update the db and I don't want it populating in the background.

tar doesn't bug me as much, provided you use unix or GNU style options. tar xvf foo.tar is just icky and less readable than tar -xvf foo.tar. I will happily concede that it's not very ergonomic though. I used to rely on things like dtrx (short for Do The Right eXtraction) because it was such a pain to remember the options for tar/unrar/unzip/7z.

You reminded me of fd. Thank you!

I got accustomed to the options for tar and 7z. for find, I just pipe it to grep or use less to search for something. It just takes time the first time you run it

Ditto for tar and unrar, although I deal with .7z so 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 -exec flag. I've spent far less time debugging in those situations since switching to fd. I won't yuck the yum of folks who are comfortable and like find, but I feel that we probably have more approachable alternatives for new users.