Show HN: A simple, fast and user-friendly alternative to find, written in Rust

Post by bm1362 » Sun, Oct 08, 2017, 9:27 PM UTC

coldtea wrote: post #69

bm1362 wrote: post #63

Earlier quoted context omitted.

I appreciate all these new incarnations of old school tools but end up sticking with the basics regardless. When I'm sshing into a box to figure out whats going on, my toolset is mostly limited to top, find, xargs, awk, grep, df, du etc. Even local development now, I'm mostly debugging on a docker container running alpine or ubuntu. Knowing the right incantations is useful in that context and keeps me from installing…

> I appreciate all these new incarnations of old school tools but end up sticking with the basics regardless. When I'm sshing into a box to figure out whats going on, my toolset is mostly limited to top, find, xargs, awk, grep, df, du etc. That's why I wrote about it being nice to have them all in distros -- perhaps in a single package like coreutils. Then wherever you are, they'd be just a "package-manager install r…

Post by nemild » Sun, Oct 08, 2017, 9:29 PM UTC

wruza wrote: post #41

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?

Post by jhasse » Sun, Oct 08, 2017, 9:33 PM UTC

bm1362 wrote: post #82

coldtea wrote: post #69

Earlier quoted context omitted.

> I appreciate all these new incarnations of old school tools but end up sticking with the basics regardless. When I'm sshing into a box to figure out whats going on, my toolset is mostly limited to top, find, xargs, awk, grep, df, du etc. That's why I wrote about it being nice to have them all in distros -- perhaps in a single package like coreutils. Then wherever you are, they'd be just a "package-manager install r…

Just my experience, I'm sure there are other types of organizations. In most of my workplaces, having one developer's preferred tools installed as a build step might not pass review. I would be annoyed if fish was installed on all our prod boxes, for example. I'm glad these tools work for you and I hope the community keeps making them, I just threw in my perspective.

Post by sharkdp » Sun, Oct 08, 2017, 9:36 PM UTC

pmoriarty wrote: post #43

I wonder how this compares to the speed of zsh's globbing, which is what I've mostly switched to using instead of find.

    > time fd -sIe jpg > /dev/null
    1,24s user 0,77s system 758% cpu 0,265 total
    
    > time ls ~/**/*.jpg > /dev/null
    0,53s user 0,97s system 98% cpu 1,518 total

Post by j2kun » Sun, Oct 08, 2017, 9:44 PM UTC

burntsushi wrote: post #65

bm1362 wrote: post #63

Earlier quoted context omitted.

I appreciate all these new incarnations of old school tools but end up sticking with the basics regardless. When I'm sshing into a box to figure out whats going on, my toolset is mostly limited to top, find, xargs, awk, grep, df, du etc. Even local development now, I'm mostly debugging on a docker container running alpine or ubuntu. Knowing the right incantations is useful in that context and keeps me from installing…

> When I'm sshing into a box to figure out whats going on, my toolset is mostly limited to top, find, xargs, awk, grep, df, du etc. I wrote some of the tools on coldtea's list, and I'm pretty much the same way in that I stick to distro tooling in vanilla setups. But I spend enough time on my local workstation that having "better" (read: creature comforts) is worth it there! But yeah, if you spend most of your time in…