114
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 20 Mar 2025
114 points (97.5% liked)
Open Source
35359 readers
226 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
- !libre_culture@lemmy.ml
- !libre_software@lemmy.ml
- !libre_hardware@lemmy.ml
- !linux@lemmy.ml
- !technology@lemmy.ml
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
This is a case where both tools are invaluable.
The original
find
has much more comprehensive options. Of course it is extensively documented and you can find all kinds of information online about how it works and how to combine it with other tools to accomplish all kinds of tasks. And it's GPL which is always preferable.fd
has a narrower range of functionality but goddamned it really is faster.fd
can run several searches on the whole hard drive's contents whilefind
is struggling to get through just a single comparable search on the same set of files. For simple tasks, the cli usage forfd
is less to remember and less to type.If I had to choose, I'd stick with
find
because it can do everything, even if it's slower and more cumbersome. But luckily, don't have to choose, just have both and use them as appropriate.