Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ripgrep 15.0

github.com

Post reply on HN
Print view View original

11–20 of 119 posts

Re: Ripgrep 15.0

#11

Post by sshine »

vessenes wrote: post #10

rg is a first for me in that it's a CLI tool that an LLM taught me about -- it's a go-to tool for Claude and codex, and since I got most of my bash skills pre-dotcom-one-boom I'm historically just a grep user. Anyway I'm trying to retrain the fingers these days, rg is super cool.

I switched to `ack` in 2017 because it handles recursive searches better.

I didn't bother switching to `ag` when it came around because of having to retrain.

But eventually I did switch to `rg` because it just has so many conveniences.

I even switched to `fd` recently instead of `find` because it's easier and less typing for common use-cases.

I've been using the terminal since 1997, so I'm happy I can still learn new things and use improved commands.

Re: Ripgrep 15.0

#13

Post by pas »

nicce wrote: post #12
CorrectHorseBat wrote: post #9

Earlier quoted context omitted.

I just found out the authors of both ripgrep and fd work for Astral, no wonder Astral makes such great software

What is the business model of Astral?

they want to build services on top of the tools

see this from ~3 months ago https://news.ycombinator.com/item?id=44358216

Re: Ripgrep 15.0

#14

Post by mort96 »

boltzmann64 wrote: post #4

Has it caught up to ugrep in terms of backward compatibility and speed yet?

I'm so happy ripgrep has a different interface to grep. I don't typically need ripgrep's better performance, I just use it because 'rg foo' does what I want 99% of the time while 'grep foo' does what I want 1% of the time.

Re: Ripgrep 15.0

#15

Post by [deleted] »

mort96 wrote: post #14
boltzmann64 wrote: post #4

Has it caught up to ugrep in terms of backward compatibility and speed yet?

I'm so happy ripgrep has a different interface to grep. I don't typically need ripgrep's better performance, I just use it because 'rg foo' does what I want 99% of the time while 'grep foo' does what I want 1% of the time.

[deleted]

Re: Ripgrep 15.0

#19

Post by opan »

mort96 wrote: post #14
boltzmann64 wrote: post #4

Has it caught up to ugrep in terms of backward compatibility and speed yet?

I'm so happy ripgrep has a different interface to grep. I don't typically need ripgrep's better performance, I just use it because 'rg foo' does what I want 99% of the time while 'grep foo' does what I want 1% of the time.

This is pretty much flipped from my experience, so I'm curious if you could expand on this. I use grep a lot to filter command output or maybe search all my txt file notes at once when I can't remember which file contained something. I use rg rarely, one example in recent memory is searching the source code for the game Barony to try to find some lesser-known console commands or behaviors (like what all drops a particular spellbook and how commonly).

Does rg work in the places grep does or is it about the type of task being done? In my examples I expect more default recursion from rg than from regular grep and I'm searching an unknown codebase with it, where as I often know my way around more or less when using regular grep.

Re: Ripgrep 15.0

#20

Post by dotancohen »

vessenes wrote: post #10

rg is a first for me in that it's a CLI tool that an LLM taught me about -- it's a go-to tool for Claude and codex, and since I got most of my bash skills pre-dotcom-one-boom I'm historically just a grep user. Anyway I'm trying to retrain the fingers these days, rg is super cool.

Through I use rg to initiate searches, my muscle memory keeps using grep after pipes.
Post reply on HN