5 ms·
Any plan to provide find compatibility for drop-in replacement? My find/locate usage patterns are not worth learning new sophisticated tool for 5sec speedup onc
by wruza 9y ago
Any plan to provide find compatibility for drop-in replacement? My find/locate usage patterns are not worth learning new sophisticated tool for 5sec speedup once a week, and I suspect that I’m not alone. This is the main problem of new tools — not repeating the old-familiar style makes it unattractive for non-aggressive users.
Side question: why is speed important? Which tools use fd to gain required performance?
- MoBattah 9y agoExactly. Especially once you've come to a good understanding with a standard *nix tool/command.
- romgrk 9y agoThe other big advantage is `more user-friendly`. Thus no backward compatibility. No doubt some people are used to the old patterns, but lots of people also prefer saner defaults.
- wruza 9y agoI couldn’t use neither thing without man page for the first time. And remembering -name -iname -type* and -I -s comes only with practice. * does fd find files by type, mtime, depth, logical operators? I missed that in readme. If not, maybe “just pattern” argument is not too fair at all.
- walkingolof 9y agoI agree, but replacing find would be very hard, not only does people except it to work in a certain way, but tons of shell scripts also.
- deleted 9y ago[deleted]
- foota 9y agoIt's probably the "I'm searching the entire disk for something" use case.
- sharkdp 9y agoThank you for the feedback. No, fd does not aim to be a drop-in replacement for find. It was actually designed as a "user-friendly" (I know, I know...) alternative to find for most of the use-cases: "fd pattern" vs. "find -iname 'pattern'", smart case, etc. Also, in my view, the colored output is not just a way to make it look fancy, but actually helps a lot when scanning a large output in the terminal. The speed is not hugely important to me, but I wanted it to be at least comparably fast to find (that's why I decided to try out Rust for this project). Otherwise, nobody would even consider using it. I know that it will not be for everyone and I also know that it's a lot to ask someone to learn a new tool, but I'm happy if there are some people that enjoy using it. I certainly do ;-)
- weaksauce 9y agoany plans on implementing the exec command from find in fd?
- sharkdp 9y agoI'm not entirely sure, yet, but I'd be happy to discuss this. A GitHub ticket would be the best place (https://github.com/sharkdp/fd/issues https://github.com/sharkdp/fd/issues).
- nine_k 9y agoWhy it would be significantly better than using a pipe?
- jimktrains2 9y agoBecause you'll have to pipe into xargs and then you have issues with spaces in file names, sometimes-exec is simpler for a single command.
- RHSeeger 9y agoYou can use -print0 and -0 to handle spaces. find . -name \*.java -print0 |xargs -0 grep something
- rcthompson 9y agoI see the speed as a secondary concern relative to the simplified interface. This tool looks like it covers about 99% of my usage of find with a much simpler and terser syntax, and I'm looking forward to trying it.
- wruza 9y agoIt is interesting if alias fd=“function _fd(){find . -iregex ‘.*’$1’.*’};_fd” would suffice for these 99? (not tested, but hope you got the idea)
- nemild 9y agoYour point expresses the classic innovator's dilemma; in this case, impossible to improve usability if you have to maintain existing SLA forever.