| ▲ | burntsushi a year ago | |
You can still chain ripgrep. I specifically designed it so that you can chain it just like you would a normal grep. It does indeed also include other functionality that might traditionally be left to other tools (like filtering files). But this is nothing that GNU grep wasn't already doing itself anyway. IMO, it's better to view the Unix philosophy as a means to an end and not an end to itself. And IMO, it's important to weigh the benefits of coupling to the user experience. | ||
| ▲ | fsckboy a year ago | parent | next [-] | |
>view the Unix philosophy as a means to an end and not an end to itself it won't be a means to an end any more if you don't preserve it, so not breaking that aspect of it has to be one of your ends. if you use it to take ls to a new place but that place is not within the ecosystem, it will be an evolutionary dead end, or worse, the first meteor in the meteor storm that ends all life. current/traditional unix may not be the be-all/end-all, but replacing it/changing it requires viewing it comprehensively and changing all the tools at once or having a plan to. A good example of this is Plan9 | ||
| ▲ | L3viathan a year ago | parent | prev | next [-] | |
I think ripgrep specifically is counted in the comment you reply to as a tool that _does_ do one thing well, and that one should use it (or grep) in combination with an ls, instead of giving ls filtering abilities. | ||
| ▲ | sudahtigabulan a year ago | parent | prev [-] | |
> You can still chain ripgrep. I specifically designed it so that you can chain it just like you would a normal grep. Headings on when isatty and off when piping the output put me off when I first tried ripgrep. I don't expect the tools to change their output format on me. Luckily, you made this behavior configurable, so I'm a happy convert now. | ||