Hacker Read top | best | new | newcomments | leaders | about | bookmarklet login

ripgrep isn't POSIX compliant. It's hardly a proper replacement.


sort by: page size:

ripgrep stole the name but doesn’t follow the posix standard.

From ripgrep's FAQ:

> Do you care about POSIX compatibility? If so, then you can't use ripgrep because it never was, isn't and never will be POSIX compatible.


Could ripgrep offer a POSIX compatible mode?

This is not POSIX compliant though.

He means it's not POSIX-compliant. You can't replace /bin/sh with it and expect stuff to work.

It cannot be a standard when it isn't part of POSIX.

And a completely incompatible non-POSIX syntax, which sounds great in theory but isn't nearly enough better to justify the departure IMHO.

OP probably meant POSIX-compliant

It's not bash or POSIX compatible at all, they're basically incompatible.

not POSIX.

More precisely, it isn't a POSIX utility.

Because nobody has written a good (universal) alternative. POSIX sh is available everywhere and is extremely well suited to gluing things together.

That's not the same thing though, is it? Even desktop Linux is not technically POSIX compliant.

There are programs that violate POSIX and are picky about it.

That is what I mean by POSIX compliant, so I stand corrected. Thanks.

let's collectively mark POSIX as deprecated and move on

Most Linux distros don't claim to be POSIX compliant. (In fact, software on GNU/Linux in general doesn't claim to be such. Sometimes it's taken as a guideline, more often ignored entirely.)

Given that most people don't use POSIX rather GNU extensions, that is besides the point.

I get where you're coming from, but there's an enormous ecosystem of software written for posix. You wouldn't just be starting over with new standards.. you'd be tossing out a whole world of software that we already have.
next

Legal | privacy