4 ms·

The table is misleading isn't it? It seems to imply that rg can't work recursively, but [1] states "..ripgrep defaults to recursive directory search...". I unde

by rozim 9y ago

The table is misleading isn't it? It seems to imply that rg can't work recursively, but [1] states "..ripgrep defaults to recursive directory search...". I understand that the table might mean that rg doesn't have a flag to enable recursive search, but surely we care about features more than flags... [1] https://github.com/BurntSushi/ripgrep#why-should-i-use-ripgrep https://github.com/BurntSushi/ripgrep#why-should-i-use-ripgr...

infodroid 9y ago
The table doesn't yet distinguish between lacking a command line flag due to absence of a feature vs due to the feature being the default. This is similar to the situation with case-sensitive search in GNU grep, which ends up with a blank cell even though it is the default. See: https://github.com/beyondgrep/website/issues/72 https://github.com/beyondgrep/website/issues/72 It's a fair criticism but I don't think it is designed to be misleading.
- fragmede 9y ago
  Maybe not designed to be misleading, but misleading nonetheless. For `grep`, `grep -i needle` is (approximately) equal to `ack/ag needle`, but looking at the table I wouldn't think grep supports case sensitivity.
  - petdance 9y ago
    I've updated the phrasing so it says "Re-enable case-sensitive search over case-insensitve or smart-case search".
bluGill 9y ago
I agree, but I know in my own project that my "competition" is moving, and I don't follow them. Thus any time like the linked one that I create quickly become out of date as they add new features.
wyldfire 9y ago
It's almost more useful as a rosetta stone than a feature comparison.
- petdance 9y ago
  Author here. Yes, that's really what it is. I need to make one that's actually feature comparison more than phrasebook. We're also working on a GNU grep vs. POSIX grep vs. BSD grep phrasebook.
  - infodroid 9y ago
    I don't think it would take very much to go from rosetta stone to a more comprehensive feature comparison. For example, the table could show the blank cell in a different color if it is a default feature, or if it an unsupported feature. Alternatively, the cell could contain a message such as "(default)".
    - petdance 9y ago
      It's going to be two pages ultimately. If you're comparing features, you don't care about the how. Right now we're keeping all the data in a JSON file that we massage into a chart. Massaging it into a true feature comparison chart, along with a rosetta stone, should be a simple matter of programming. Same thing with the GNU/POSIX/BSD rosetta stone we're working on. https://github.com/beyondgrep/website/blob/dev/comparison.json https://github.com/beyondgrep/website/blob/dev/comparison.js...

by rozim 9y ago

infodroid 9y ago

The table doesn't yet distinguish between lacking a command line flag due to absence of a feature vs due to the feature being the default. This is similar to the situation with case-sensitive search in GNU grep, which ends up with a blank cell even though it is the default. See: https://github.com/beyondgrep/website/issues/72 https://github.com/beyondgrep/website/issues/72 It's a fair criticism but I don't think it is designed to be misleading.

fragmede 9y ago
Maybe not designed to be misleading, but misleading nonetheless. For `grep`, `grep -i needle` is (approximately) equal to `ack/ag needle`, but looking at the table I wouldn't think grep supports case sensitivity.
- petdance 9y ago
  I've updated the phrasing so it says "Re-enable case-sensitive search over case-insensitve or smart-case search".

bluGill 9y ago

I agree, but I know in my own project that my "competition" is moving, and I don't follow them. Thus any time like the linked one that I create quickly become out of date as they add new features.

wyldfire 9y ago

It's almost more useful as a rosetta stone than a feature comparison.

petdance 9y ago
Author here. Yes, that's really what it is. I need to make one that's actually feature comparison more than phrasebook. We're also working on a GNU grep vs. POSIX grep vs. BSD grep phrasebook.
- infodroid 9y ago
  I don't think it would take very much to go from rosetta stone to a more comprehensive feature comparison. For example, the table could show the blank cell in a different color if it is a default feature, or if it an unsupported feature. Alternatively, the cell could contain a message such as "(default)".
  - petdance 9y ago
    It's going to be two pages ultimately. If you're comparing features, you don't care about the how. Right now we're keeping all the data in a JSON file that we massage into a chart. Massaging it into a true feature comparison chart, along with a rosetta stone, should be a simple matter of programming. Same thing with the GNU/POSIX/BSD rosetta stone we're working on. https://github.com/beyondgrep/website/blob/dev/comparison.json https://github.com/beyondgrep/website/blob/dev/comparison.js...