Ripgrep 15.0.0
25 comments
·October 18, 2025Fethbita
dizhn
What I like about both is their defaults without any parameters are what i would need them for 99% of the time. Huge time saver.
rg <string>
fd <string>
CorrectHorseBat
I just found out the authors of both ripgrep and fd work for Astral, no wonder Astral makes such great software
nicce
What is the business model of Astral?
pas
they want to build services on top of the tools
see this from ~3 months ago https://news.ycombinator.com/item?id=44358216
2bitencryption
the ripgrep codebase is ultimate “pour a drink, settle into your coziest chair, and read some high quality software” codebase. Just click around through it and marvel.
davoneus
Great tool, and incredibly easy to use. Started with it on Linux, and now use on 'doze too.
Probably the singular reason why I finally use regex as the first search option, rather than turning to it after bruting thru a search with standard wildcards.
vessenes
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.
sshine
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.
dotancohen
Sell me on fd. I occasionally use find, mostly with the -name or -iname flags.
rkomorn
It feels nearly instant by comparison to find. That's been enough for me.
dotancohen
Through I use rg to initiate searches, my muscle memory keeps using grep after pipes.
IlikeMadison
That's what I call quality software.
jodedwards
ripgrep 15 is a new major version release of ripgrep that mostly has bug fixes, some minor performance improvements and minor new features.
boltzmann64
Has it caught up to ugrep in terms of backward compatibility and speed yet?
burntsushi
Backcompat with what? ripgrep was, is and will never be POSIX compatible: https://github.com/BurntSushi/ripgrep/blob/master/FAQ.md#can...
Aa for ugrep, flipping the question around would be more appropriate. ugrep has caught up with ripgrep in some common cases, but not all.
dgacmu
This seems like an unhelpful comment?
First of all, the ugrep performance comparisons are online (and haven't been updated to compare against this version that was only released 3 days ago). So your question is answerable:
https://github.com/Genivia/ugrep-benchmarks
The two are very close and both are head and shoulders faster than most other options.
And backwards compatibility is a mixed thing, not a mandatory goal. It's admirable that ugrep is trying to be a better drop-in replacement. It's also cool that ripgrep is trying to rethink the interface for improving usability.
(I like ripgrep in part because it has different defaults than grep that work very well for my use cases, which is primarily searching through codebases. The lack of backwards compatibility goes both ways. Will we see a posix ripgrep? Probably not. Is ripgrep a super useful and user-friendly tool? Definitely.)
mort96
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.
opan
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.
null
jodedwards
> ripgrep 15 is a new major version release of ripgrep that mostly has bug fixes, some minor performance improvements and minor new features.
Lol, "major" release with minor this and minor that.
Why semver at all?
burntsushi
The most important part of semver is that breaking changes are indicated by incrementing the major version. semver does not say that the major version must only be incremented when a breaking change is present.
jvuygbbkuurx
Bugfixes can be breaking changes
o_m
I don't think they claim they are using semver. Lots of companies/projects use "major" releases just for the added hype.
kortilla
People write scripts that call ripgrep. That makes the arguments an API.
Semver is useful to indicate breaking API changes.
Not sure if they are following semver, but that is the argument for using semver in a cli tool.
Just like fd, I actually enjoy using rg and like these new set of command line tools.