<story><title>Why GNU grep is fast (2010)</title><url>https://lists.freebsd.org/pipermail/freebsd-current/2010-August/019310.html</url></story><parent_chain><item><author>heywoodlh</author><text>Ripgrep has always been interesting to me as I don&amp;#x27;t ever find myself bothered by the speeds of GNU grep, even when working with large files.  Additionally, grep is a standard utility included on most Unix-like OS-es so it is not super risky to write a script that relies on grep -- in contrast to writing a script that relies on a not-usually-installed-by-default tool like ripgrep. For me, I just don&amp;#x27;t have issues with grep!&lt;p&gt;I&amp;#x27;d love to hear people&amp;#x27;s experiences on how grep wasn&amp;#x27;t adequate and why they use ripgrep instead.&lt;p&gt;(This is not a criticism of Ripgrep: I&amp;#x27;m glad it exists and that other people find it useful.)</text></item><item><author>epage</author><text>See also &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.burntsushi.net&amp;#x2F;ripgrep&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.burntsushi.net&amp;#x2F;ripgrep&lt;/a&gt; which contrasts ripgrep with GNU grep and others (from 2016)</text></item></parent_chain><comment><author>ydant</author><text>For me the big advantage of ripgrep is it defaults to searching recursively so I can just do &amp;quot;rg term&amp;quot;.&lt;p&gt;And the plugins support, which enables something like ripgrep-all, which can then search PDFs, etc.&lt;p&gt;If I&amp;#x27;m scripting, though, I try to stick to common denominator grep.</text></comment>
<story><title>Why GNU grep is fast (2010)</title><url>https://lists.freebsd.org/pipermail/freebsd-current/2010-August/019310.html</url></story><parent_chain><item><author>heywoodlh</author><text>Ripgrep has always been interesting to me as I don&amp;#x27;t ever find myself bothered by the speeds of GNU grep, even when working with large files.  Additionally, grep is a standard utility included on most Unix-like OS-es so it is not super risky to write a script that relies on grep -- in contrast to writing a script that relies on a not-usually-installed-by-default tool like ripgrep. For me, I just don&amp;#x27;t have issues with grep!&lt;p&gt;I&amp;#x27;d love to hear people&amp;#x27;s experiences on how grep wasn&amp;#x27;t adequate and why they use ripgrep instead.&lt;p&gt;(This is not a criticism of Ripgrep: I&amp;#x27;m glad it exists and that other people find it useful.)</text></item><item><author>epage</author><text>See also &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;blog.burntsushi.net&amp;#x2F;ripgrep&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;blog.burntsushi.net&amp;#x2F;ripgrep&lt;/a&gt; which contrasts ripgrep with GNU grep and others (from 2016)</text></item></parent_chain><comment><author>wantoncl</author><text>Unicode support. It might have been the Windows ports of grep that were the problem, but ripgrep shines with Unicode files. And it handles a mix of Unicode and ASCII files without issue.&lt;p&gt;And I totally agree that having grep installed everywhere and it&amp;#x27;s pretty fast enough. But I had a few ripgrep searches that were genuinely eyeblink fast. Like my finger hadn&amp;#x27;t fully lifted off the enter key and it was done. On 10K+ plus files, about 1 GB, with 1.5M+ LOC. And the default folder recursion and .gitignore handling is a plus.</text></comment>