diff options
| author | Andrew Gallant <jamslam@gmail.com> | 2017-09-04 11:14:57 -0400 |
|---|---|---|
| committer | Andrew Gallant <jamslam@gmail.com> | 2017-09-04 11:15:14 -0400 |
| commit | f9cbf7d3d4febc44e7834003eec1f25498da111f (patch) | |
| tree | 2496d1c7150c99523db4311e3d7d3c2e2371786c /README.md | |
| parent | 7eb1dd129ed8b5f98553d4e468a16b69cead129a (diff) | |
tweak working
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 8 |
1 files changed, 4 insertions, 4 deletions
@@ -71,9 +71,9 @@ increases the times to `3.081s` for ripgrep and `11.403s` for GNU grep. ### Why should I use `ripgrep`? -* It can replace both The Silver Searcher and GNU grep because it is faster - than both. (N.B. It is not, strictly speaking, a "drop-in" replacement for - both, but the feature sets are far more similar than different.) +* It can replace both The Silver Searcher and GNU grep because it is generally + faster than both. (N.B. It is not, strictly speaking, a "drop-in" replacement + for both, but the feature sets are far more similar than different.) * Like The Silver Searcher, `ripgrep` defaults to recursive directory search and won't search files ignored by your `.gitignore` files. It also ignores hidden and binary files by default. `ripgrep` also implements full support @@ -118,7 +118,7 @@ multiline search, then `ripgrep` may not quite meet your needs (yet). ### Is it really faster than everything else? -Yes. A large number of benchmarks with detailed analysis for each is +Generally, yes. A large number of benchmarks with detailed analysis for each is [available on my blog](http://blog.burntsushi.net/ripgrep/). Summarizing, `ripgrep` is fast because: |