3 ms·

What does this tool provide that I can't get from a wrapper around gnu find?

by sagartewari01 8y ago

ethelward 8y ago
What does GNU find provides that I can't get from a wrapper around Perl?
baq 8y ago
probably nothing, is that a problem?
- scbrg 8y ago
  Not a problem, but it's still a valid question. I'm all for people writing alternatives to existing tools. I've done so myself multiple times. But when you start promoting your alternative, "so what's does it do better?" is a very reasonable question for other people to ask. After all, they are the ones who need to invest time in learning the new tool, perhaps add it as a dependency in their tool chain/work flow - with all the downsides that has.
  - atoav 8y ago
    The readme states it is ~3 to 5 times faster. And it seems to have a more beginner friendly syntax. I am not aperson who just has to use the newest and gratest for the sake of it, but I’d take ripgrep/rg over grep whenever I have the choice.
rkangel 8y ago
If nothing else - ability to easily compile for native Windows and work as expected (with no Cygwin/GnuWin32 fun).
olejorgenb 8y ago
- It frees you from writing the wrapper (duh) - It probably have more niceties than a 5min wrapper (color, friendly defaults, etc.) I've personally used a homemade find wrapper for years, but have now replaced it with `fd` (another find reimplementation). The advantages isn't huge, but I find the niceties I never bothered implementing - well - nice :) That being said: I did get burned by the default behavior of ignoring hidden files :D Would've been nice if it by default didn't show hidden matches, but printed on stderr - something like: $ fd thing foo/something ... >searching hidden files - ^C to abort< >hidden files found (29) - use `--hidden` to show<
mbaeten 8y ago
It might also be valuable to projects like Redox.
- vishaltelangre 8y ago
  Related discussion - https://www.reddit.com/r/rust/comments/av31ae/ff_find_files_by_name/ehcanyn/ https://www.reddit.com/r/rust/comments/av31ae/ff_find_files_....

What does this tool provide that I can't get from a wrapper around gnu find?

ethelward 8y ago

What does GNU find provides that I can't get from a wrapper around Perl?

baq 8y ago

probably nothing, is that a problem?

scbrg 8y ago
Not a problem, but it's still a valid question. I'm all for people writing alternatives to existing tools. I've done so myself multiple times. But when you start promoting your alternative, "so what's does it do better?" is a very reasonable question for other people to ask. After all, they are the ones who need to invest time in learning the new tool, perhaps add it as a dependency in their tool chain/work flow - with all the downsides that has.
- atoav 8y ago
  The readme states it is ~3 to 5 times faster. And it seems to have a more beginner friendly syntax. I am not aperson who just has to use the newest and gratest for the sake of it, but I’d take ripgrep/rg over grep whenever I have the choice.

rkangel 8y ago

If nothing else - ability to easily compile for native Windows and work as expected (with no Cygwin/GnuWin32 fun).

olejorgenb 8y ago

- It frees you from writing the wrapper (duh) - It probably have more niceties than a 5min wrapper (color, friendly defaults, etc.) I've personally used a homemade find wrapper for years, but have now replaced it with `fd` (another find reimplementation). The advantages isn't huge, but I find the niceties I never bothered implementing - well - nice :) That being said: I did get burned by the default behavior of ignoring hidden files :D Would've been nice if it by default didn't show hidden matches, but printed on stderr - something like: $ fd thing foo/something ... >searching hidden files - ^C to abort< >hidden files found (29) - use `--hidden` to show<

mbaeten 8y ago

It might also be valuable to projects like Redox.

vishaltelangre 8y ago
Related discussion - https://www.reddit.com/r/rust/comments/av31ae/ff_find_files_by_name/ehcanyn/ https://www.reddit.com/r/rust/comments/av31ae/ff_find_files_....