3 ms·

> I feel like if you're going to make a new grep and put a web page for it, your webpage should start with why your grep is better than the default (or all the

> I feel like if you're going to make a new grep and put a web page for it, your webpage should start with why your grep is better than the default (or all the other ones). No snark here, but is the subtitle not enough to start? "a more powerful, ultra fast, user-friendly, compatible grep"

fsckboy 3y ago
no snark here, but the subtitle was the start of my confusion: what does "user-friendly" mean in the context of grep, and why should I believe the claim? regular expressions are not friendly, but the user friendly way for a cli filter to behave is to return retvals appropriately, output to stdout, error messages to stderr... does user friendly mean copious output to stderr? what else could it possibly mean? do I want copious output to stderr?
- infamia 3y ago
  > no snark here, but the subtitle was the start of my confusion: what does "user-friendly" mean in the context of grep, and why should I believe the claim? Granted, it is far from a thing of beauty, but there is a large, captioned screenshot of the included text user interface just beneath. Then again, it is a website for a command line tool. "Many Bothans died to bring us this information."
jedberg 3y ago
Not really. * a more powerful -- This is meaningless without some sort of examples. Powerful how? What does it do that's better than grep? * ultra fast -- This at least means something, but it should be quantified in some way. "50%+ faster for most uses cases" or something like that. * user-friendly -- not even sure what this means. Seems kind of subjective anyway. I find grep plenty user friendly, for a command line tool. * compatible grep -- I mean, they all are pretty much, but I guess it's good to know this?
- infamia 3y ago
  > * ultra fast -- This at least means something, but it should be quantified in some way. "50%+ faster for most uses cases" or something like that. That would be begging for nerd rage posts, just like so many disputing the benchmarks. >:D > * user-friendly -- not even sure what this means. Seems kind of subjective anyway. I find grep plenty user friendly, for a command line tool. Just below is a huge, captioned screenshot of the TUI? > * compatible grep -- I mean, they all are pretty much, but I guess it's good to know this? One would think so... but I have so many scars concerning incompatibilities with different versions of grep (as do others in the comments). If you don't know, then that feature isn't listed for you. :)

fsckboy 3y ago

no snark here, but the subtitle was the start of my confusion: what does "user-friendly" mean in the context of grep, and why should I believe the claim? regular expressions are not friendly, but the user friendly way for a cli filter to behave is to return retvals appropriately, output to stdout, error messages to stderr... does user friendly mean copious output to stderr? what else could it possibly mean? do I want copious output to stderr?

infamia 3y ago
> no snark here, but the subtitle was the start of my confusion: what does "user-friendly" mean in the context of grep, and why should I believe the claim? Granted, it is far from a thing of beauty, but there is a large, captioned screenshot of the included text user interface just beneath. Then again, it is a website for a command line tool. "Many Bothans died to bring us this information."

jedberg 3y ago

Not really. * a more powerful -- This is meaningless without some sort of examples. Powerful how? What does it do that's better than grep? * ultra fast -- This at least means something, but it should be quantified in some way. "50%+ faster for most uses cases" or something like that. * user-friendly -- not even sure what this means. Seems kind of subjective anyway. I find grep plenty user friendly, for a command line tool. * compatible grep -- I mean, they all are pretty much, but I guess it's good to know this?

infamia 3y ago
> * ultra fast -- This at least means something, but it should be quantified in some way. "50%+ faster for most uses cases" or something like that. That would be begging for nerd rage posts, just like so many disputing the benchmarks. >:D > * user-friendly -- not even sure what this means. Seems kind of subjective anyway. I find grep plenty user friendly, for a command line tool. Just below is a huge, captioned screenshot of the TUI? > * compatible grep -- I mean, they all are pretty much, but I guess it's good to know this? One would think so... but I have so many scars concerning incompatibilities with different versions of grep (as do others in the comments). If you don't know, then that feature isn't listed for you. :)