fd VS ripgrep

I know that if you want `fd` (https://github.com/sharkdp/fd) you need to `apt install fd-find` and which installs the binary `fdfind` (!).

fd is a friendlier, faster alternative to find, with sensible defaults and clean output.

sharkdp/fd

fd find replacement

GitHub: https://github.com/sharkdp/fd

3. find → fd (39.5k ⭐)

fd GitHub

It's not just the OS itself, where some of the slowness can at least be explained by the silo-ed nature of development and the large amount of moving parts. But even when MS gives a small-ish team free reign and a fresh start, the software is just agonizingly slow and buggy.

Example 1: new PowerToys https://github.com/microsoft/PowerToys/

The FancyZones "window snap" UI takes upwards of half a second to activate when dragging a window and the Zone Editor is at around 5s. All in all it is only very slightly less buggy than 3rd party tiling WMs like komorebic.

The PowerToysRun utility input is extremely variable, takes between 1 and 20(!) seconds. A lot of the plugins shipped with it simply don't work or have no suggestions/hints once you enter their prefix. The search relies on WindowsSearch, which is about 500x slower than https://github.com/sharkdp/fd and has not improved since Win7. Who cares, nobody ever searches for files, right? As a whole, PTRun is simply worse than https://github.com/Flow-Launcher/Flow.Launcher which uses the same UI kit as far as I can see. WTF?

I'm the author of Biff. I just wanted to leave a really cool example of something that Biff can do that I _think_ is kinda hard to do otherwise. (And also, I want to make an assertion about it and I hope this will lead to me being wrong and learning something new.)

The use case is: "I want to see a list of all files in a repository, sorted in ascending order of when it was most recently changed according to source control. I also want to highlight the time with color, make it be in local time and format it in my own bespoke way using strftime." Here's the full command (run from the root of https://github.com/BurntSushi/ripgrep):

    $ git ls-files \

For full-text search, ripgrep is faster than any in-app search I've used:

ripgrep – A fancier version of grep commonly used by coding tools.

After finding files, I usually need to search inside them. For that, ripgrep, usually called rg, is my default.

Ah yes... its `-E`.

But fastmod, which is mentioned in at the end of https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#search-and-replace is surprisingly good, both in terms of performance/ux and compatibility.

You just:

  fastmod -m 'something I need to (change|break)' '$1 is inevitable'

BurntSushi/ripgrep

ripgrep needs no introduction. It's grep, but fast. Respects .gitignore, searches recursively by default, and returns results before you finish blinking.

Ripgrep does something like thhis. It has a meta regex engine that switches engine when it finds what looks like pathological cases (or rather, the regex-automata crate does, which is used by the regex crate, which powers ripgrep).

https://docs.rs/regex-automata/latest/regex_automata/meta/st...

Ripgrep in turn exposes some knobs to tweak the heuristics

https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#how...