I'm trying to sort out what the complaints were about. Was it that it was poorly written? I didn't look at the code, but that doesn't feel like the kind of implementation that would draw attention.
Was it that it was pushed as something revolutionary? I didn't see any of that either.
I have probably written a half dozen utilities just like this. But never published one. They are one-off tools that end up being two-off then more.
The "Why not use grep" is a bit strange. Grep doeesn't do search/replace does it? And not all OSes have grep out of the box (On windows, I usually end up getting ripgrep, but I sure don't get a ripsed to go with it). Having a search/replace command line tool with a good regex syntax (good as in not Perl) would be fantastic. Even better if it would be a self contained executable and not requiring node - but I can see that a node tool would be useful for someone who often has node available on their machine.
Was the ridicule chiefly based on that it was made in Node.js? It's my best guess, but wth?
If anything deserves ridicule, it's this (which are the two most upvoted answers from stackoverflow on how to replace using grep). Does anyone look at this and say "well, this looks fine, can't see how that could be any less obscure"
find /path/to/files -type f -exec sed -i 's/oldstring/new string/g' {} \;
grep -rl matchstring somedir/ | xargs sed -i 's/string1/string2/g'
Was it that it was pushed as something revolutionary? I didn't see any of that either. I have probably written a half dozen utilities just like this. But never published one. They are one-off tools that end up being two-off then more.
The "Why not use grep" is a bit strange. Grep doeesn't do search/replace does it? And not all OSes have grep out of the box (On windows, I usually end up getting ripgrep, but I sure don't get a ripsed to go with it). Having a search/replace command line tool with a good regex syntax (good as in not Perl) would be fantastic. Even better if it would be a self contained executable and not requiring node - but I can see that a node tool would be useful for someone who often has node available on their machine.
Was the ridicule chiefly based on that it was made in Node.js? It's my best guess, but wth?
If anything deserves ridicule, it's this (which are the two most upvoted answers from stackoverflow on how to replace using grep). Does anyone look at this and say "well, this looks fine, can't see how that could be any less obscure"