129 ms·
If you're already proficient with grep, find, etc - there's not much reason to switch. As I said elsewhere: I never managed to use find because I always had to
by BeetleB 2y ago
If you're already proficient with grep, find, etc - there's not much reason to switch. As I said elsewhere:
I never managed to use find because I always had to look up command line arguments. I would always find a different way to solve my problem (e.g. Midnight Commander).
I use fd all the time.
A better interface makes a big difference.
- thayne 2y ago> there's not much reason to switch There are a few reasons you might still want to switch. In fd'a case: - It respects .gitignore files (as well as similar .fdignore files that aren't git specific), which can help you find what you care about without a lot of noise, or having to pass a lot of exclude rules to find - it can search in parallel, which can significantly reduce latency when searching large directories. However, there are also reasons you might want to keep using find: - fd can't do everything find can. fd is intended to replace the most common use cases with a simpler interface, but there are many less common cases that require finds greater flexibility. In fact, I still use find sometimes because of this. - find is more likely to already be installed
- theragra 2y agoBy the way, FAR manager was ported to Linux quite a long time ago, but I forgot about it. Recently I remembered and installed it. Not too hard to install (although you need to use third party repos sometimes). And then - voila - a lot of convenience for dinosaurs from Norton Commander era like myself, who cant remember cli tools syntax that well.