ripgrep

“Going from ag to ripgrep is not unequivocally better. Sure ripgrep is faster, but its file filtering using -g is so much more cumbersome than -G in ag.”

“Whole LLM agent tool call with ripgrep gives 99% use cases right lol”

“He keeps using -r with ripgrep thinking that means recursive, when actually that's a replacement instruction”

“when they do work (which is 99%+ of the time for most users), they are significantly more pleasant to work with.”

“seems to always wind up being faster and better than something like”

“ripgrep will give you basically all the same query features just by being fast”

“That's a really good example. The specific detail is that node_modules isn't something I want results from while I'm grepping around.”

“I see the future where I'm faster with Neovim and ripgrep than Codex”

“`cd ripgrep; cargo install --path .` or `cargo install ripgrep` usually just work”

“manual ripgrep exploration is really effective of getting codebases”

“You can give your agent ripgrep and let it figure out how to find the right results all on its own.”

“The agents do just fine using ripgrep and calling cargo clippy, dart analyze, ty check, etc. themselves.”

“ripgrep helps, so it makes sense to add a line about it into some memory file”

“You should place this energy with something like ripgrep, not a company with huge funding that actually depends on people using their product.”

“ivy/avy/counsel/swiper with ripgrep (thanks burntsushi ) integration”

“ripgrep - or at worst, grep with LC_ALL=C - is much, much faster than any aggregation tool”

“I experienced a data truncation issue where I ran an rg -zF fixed string search piped into another rg -F.”

“in non-git repos, .gitignore rules are silently ignored because rg doesn't pass --no-require-git by default”

“ripgrep is inefficient in CPU usage when runs multithreaded and uses about 2x times more CPU time”

“ripgrep shows that that bundling together stuff sometimes does end up with a user experience that people prefer”

“On a mid-size codebase, I fzf- and rg-ed through the code almost instantly”

“too many things get ignored and I can't be bothered to figure out how to configure it more cleanly”

“Often, the return was caused by a frustration of not having the new tools installed on the random server I sshed to.”

“You could easily just alias a command with the right flag if the capability was opt-in.”

“Using another tool's config by default, making it difficult/impossible to use the dedicated config is the most annoying thing I can imagine.”

“incompatible with grep syntax, which makes it useless to most system admins”

“it happily used all of my cpu cores scanning files, made me unable to do anything for awhile”

“rg using implicit '.ignore' file (a super-generic name instead of a proper tool-specific config)”

“I wouldn't want to use tools that straddle the two, unless they had a nice clear way of picking one or the other.”

“rg x would show nothing but grep -r x showed the lines for any x”

“I still use it but Ive never trusted it fully since then I double check.”

“rg is the number one most important part that enables LLMs to be smart agents in a codebase”

“Really dislike it defaulting to that ignoring files that are ignored by git.”

“it makes searching for text inside the current folder so much easier and it is insanely faster”

“Direct tool calls are faster, more reliable, and the intermediate exploration steps are ephemeral scaffolding anyway.”

“Ripgrep is much faster than grep. But the result is not more concise and tokens are wasted.”

“From my daily-use utilities, ripgrep and bat seem to have zero dependencies.”

“Full text search or even grep/rg are a lot faster and cheaper to work with”

“runs async and finishes more or less before my "emacs pinkie" is ready to touch another key”

“You don't need wsl, just install rigrep or the powershell equivalent of find”