Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>what was the flag I need for `find` again

This is not on you, `find`'s command line syntax is awful even if you have to use it everyday.



> `find`'s command line syntax is awful

What's awful about it?


Everything? It, just like tar, don't follow the convention of many other CLI utilities.

That alone is why I prefer `fd` or plocate for most tasks I previously used find for.


Never heard of plocate but I thought fd a step down from find; it's very limited in functionality, colorful output alone can't justify that.

> [It doesn't] follow the convention of many other CLI utilities.

Because unlike other CLI utilities, find evaluates an expression specified as arguments. Maybe a small DSL like JQ would be better, but how would you embed shell code in it? Meh.


Find has its uses, I use it frequently to correct improper unix file permissions and owners and when I need to execute a command on a list of files.

However for the vast majority of queries, I'm only looking for something based on the filename, and that's where having sane regex and standard argument structure (like fd has) is great.


> for the vast majority of queries, I'm only looking for something based on the filename

I'd manage with find|grep but yes, nothing wrong with wanting something more compact.

> sane regex

For me that's POSIX ERE, I don't know which flavor fd uses.


And don’t forget GNU vs BSD version differences…


That’s why you install gnu-coreutils. Eliminate the difference.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: