3 ms·
Yeah and its also 10 times larger https://github.com/BurntSushi/ripgrep/issues/1481 https://github.com/BurntSushi/ripgrep/issues/1481
by svnpenn 7y ago
Yeah and its also 10 times larger
https://github.com/BurntSushi/ripgrep/issues/1481 https://github.com/BurntSushi/ripgrep/issues/1481
- detaro 7y agothe previous issue on the topic has some pointers
- dharmab 7y agoWhich is absolutely a good trade-off for a modern desktop system.
- reificator 7y agoIf you go on a system with grep aliased and run your single grep command, are you going to be able to tell which binary was larger? If you look at the size of two disk images for different distros, and one has grep while the other has ripgrep, are you going to be able to tell which is which? 10x larger than grep is noise in 2020. Making that tradeoff in exchange for significantly improved performance seems reasonable. Not to mention a large part of that difference is likely due to grep relying on libc, while ripgrep has to bundle its own runtime. And that's not even bringing up memory safety. I'll take ripgrep at 10x the size of grep any day.
- burntsushi 7y agoYes. If that disk space is more important to you than correctness, performance and better Unicode support, then yeah, you should definitely keep using the silver searcher. I gave more details in a response on that issue: https://github.com/BurntSushi/ripgrep/issues/1481#issuecomment-583844339 https://github.com/BurntSushi/ripgrep/issues/1481#issuecomme...