And you can look to ripgrep to learn how to produce one! And in particular, how to do it without duplicating docs.
In any case, my point is that maybe there is a more expansive viewpoint here that makes sense instead of honing down on to something hyper specific.
> It's nothing missing, it's just different for no clear reason, and that means remembering different syntaxes depending on which tool I am using at the moment.
Right, so you want a POSIX compatible tool because POSIX is what you're used to and you don't want to use any other interface. Which is fine. Keep using the old stuff. I don't see any good reason to exactly imitate POSIX when I can go build something that I think is better without being constrained by POSIX. For example, I think just having \b is better than having both \< and \>.
> I just think it was a bad example.
I don't. There's a lot that tools like ripgrep and fd do that the old tools don't do that turn it into its own niche. Like enabling "smart" filtering by default and other things that many consider to be quality of life improvements. So if you're in that niche, then looking to those tools for what they do is a good idea.