Why GNU grep is fast (2010)

Re:Why GNU grep is fast (2010) by staticassertion on Sunday July 24, 2022 @11:53AM (#32214645)

Have you worked in a monorepo? There can be 100kloc or more, easily, as well as tens or hundreds of gigabytes for build artifacts/ compilation artifacts, etc that you'll want to skip over.

For scripts I'll still use grep sometimes for the portability reason, naturally.

[ Parent | on HN ]

Re:Why GNU grep is fast (2010) by heywoodlh on Sunday July 24, 2022 @02:32PM (#32216263)

I have not worked in a monorepo. But that seems to be a great place to use `ripgrep`.

[ Parent | on HN ]

Re:Why GNU grep is fast (2010) by staticassertion on Sunday July 24, 2022 @03:16PM (#32216652)

That's probably the #2 thing for me. The other is that I have a `~/workspace` where I put all of my projects and sometimes I ripgrep through there.

[ Parent | on HN ]

Re:Why GNU grep is fast (2010) by marcinreal on Sunday July 24, 2022 @03:32PM (#32216795)

It doesn't even have to be a monorepo to see the speed difference. In Emacs I frequently invoke a thing where it searches my codebase as I type. With ripgrep, the results update almost instantaneously. ag, the silver searcher, is the second fastest thing I've used, but there would be a noticeable lag in updating the results as I typed, even for smaller repos.

[ Parent | on HN ]

Re:Why GNU grep is fast (2010) by jrockway on Sunday July 24, 2022 @05:58PM (#32218196)

What's the emacs thing? I use deadgrep but your thing sounds better.

[ Parent | on HN ]

Re:Why GNU grep is fast (2010) by abzug on Sunday July 24, 2022 @08:06PM (#32219113)

My hunch is consult-ripgrep or counsel-rg.

[ Parent | on HN ]

Re:Why GNU grep is fast (2010) by marcinreal on Monday July 25, 2022 @05:03AM (#32222090)

consult-ripgrep as the other commenter said. Before that it was helm-rg.

[ Parent | on HN ]