2 ms·

No, the most common use cases for the people using a tool designed to more easily search source code. Notice that the examples on its site show searching the Li

No, the most common use cases for the people using a tool designed to more easily search source code. Notice that the examples on its site show searching the Linux source code. For that matter, the very first sentence on that site says “ripgrep recursively searches directories for a regex pattern while respecting your gitignore” Grep still exists, unchanged. It does what you want it to. Ripgrep is a new tool designed for a different use case. It’s not about failure modes. Ripgrep isn’t failing when it doesn’t show you the files it tells you it’s going to skip in the very first line of its description. Again, you don’t have to use it if its advertised purpose doesn’t line up with what you want.

godelski 2y ago
> For that matter, the very first sentence on that site says I'd rather not go in circles. Please refer back to the original post as I addressed this. See package managers and word of mouth. Do you really visit the website or GitHub page for every tool you install? I'd be surprised if you did. Also, why is it not okay that the design was wrong? That doesn't make it a bad project. But we can recognize that choices could have been better. Those are different things. It's learning from the past https://en.wikipedia.org/wiki/Principle_of_least_astonishment https://en.wikipedia.org/wiki/Principle_of_least_astonishmen...
- kstrauser 2y ago
  Do I read the manual of every tool I use before counting on it? Yes, absolutely. The first sentence of ripgrep's man page's description section is: ripgrep (rg) recursively searches the current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files. You cannot pick up a tool, start using it without understanding what it does, then tell the tool that it's doing things wrong.
  - godelski 2y ago
    > Do I read the manual of every tool I use before counting on it? Yes, absolutely. Sorry I'm not sure I believe you and even if you are that rare case, I think you know most people don't. I'm a manual lover myself but haven't read all the manuals of all the tools I use. That would be extremely cumbersome given the sheer amount and the complexity of some tools. > You cannot pick up a tool, start using it without understanding what it does I don't disagree with the exact words but I do with what I think you're arguing. Lots of tools have a natural design where you can intuit their usage. A hammer or screwdriver is a great example. Many videogames also teach you how to play via level design without the need for tutorials (there's also many many terrible examples from video games and many sub par ones too). And that's what I'm arguing about when I'm talking about the direction of error. There's a natural signal coming back to the user so they know if something is wrong or isn't. But letting users think things are good when they aren't is an extremely costly error.

godelski 2y ago

> For that matter, the very first sentence on that site says I'd rather not go in circles. Please refer back to the original post as I addressed this. See package managers and word of mouth. Do you really visit the website or GitHub page for every tool you install? I'd be surprised if you did. Also, why is it not okay that the design was wrong? That doesn't make it a bad project. But we can recognize that choices could have been better. Those are different things. It's learning from the past https://en.wikipedia.org/wiki/Principle_of_least_astonishment https://en.wikipedia.org/wiki/Principle_of_least_astonishmen...

kstrauser 2y ago
Do I read the manual of every tool I use before counting on it? Yes, absolutely. The first sentence of ripgrep's man page's description section is: ripgrep (rg) recursively searches the current directory for a regex pattern. By default, ripgrep will respect your .gitignore and automatically skip hidden files/directories and binary files. You cannot pick up a tool, start using it without understanding what it does, then tell the tool that it's doing things wrong.
- godelski 2y ago
  > Do I read the manual of every tool I use before counting on it? Yes, absolutely. Sorry I'm not sure I believe you and even if you are that rare case, I think you know most people don't. I'm a manual lover myself but haven't read all the manuals of all the tools I use. That would be extremely cumbersome given the sheer amount and the complexity of some tools. > You cannot pick up a tool, start using it without understanding what it does I don't disagree with the exact words but I do with what I think you're arguing. Lots of tools have a natural design where you can intuit their usage. A hammer or screwdriver is a great example. Many videogames also teach you how to play via level design without the need for tutorials (there's also many many terrible examples from video games and many sub par ones too). And that's what I'm arguing about when I'm talking about the direction of error. There's a natural signal coming back to the user so they know if something is wrong or isn't. But letting users think things are good when they aren't is an extremely costly error.