Majority SJW are hypocrites, they spend all their energy and time battling against shit that's minor. Like changing the name of repos, removing certain words from a massive project etc. Making sure certain peoples feelings are protected.
Yet when it comes to serious problems in our world, like Uyghur muslims being persecuted they remain silent. Or when western countries destroy Libya and give birth slavery in Africa, they remain silent.
I don't think your mental model of the behavior of "social justice warriors" is accurate. Do you really think the people you demonize for expressing sympathy for people outside their own tribe are silent in these cases and the people you implicitly praise for keeping silent about injustices they do not suffer themselves are the heroes complaining on the internet about the treatment of the Uighurs?
libripgrep isn't currently a thing (not merged to mainline). On reddit, the author noted that ripgrep (and other utilities) need to be on the PATH, which is one of the issues related to windows packaging.
libripgrep has been on master since 0.10.0. There just isn't any high level documentation for it.
It's not clear whether libripgrep would be a good fit for this project or not. They would need to reroll all the arg parsing logic themselves. libripgrep is really about building your own search tools (or more specialized tools) using the same internal infrastructure as ripgrep. But yeah, this is why I need high level docs to explain this stuff. I've been putting it off until I get bstr straightened out.
> It's not clear whether libripgrep would be a good fit for this project or not
I actually looked into using libripgrep for this, but then I decided not to because of (a) not wanting to handle arg parsing myself (ripgrep has sooo many arguments), (b) missing or hard to find documentation.
The main reason it might be a good idea is because currently ripgrep does not know at all about a single file returning multiple "files", and all line prefixes are "hardcoded" (e.g. Page X: hello in pdfs is just prefixed per line). Also I can't rely on ripgrep's binary detection currently, because it would have to happen for "parts of files" from the perspective of ripgrep.
It would be great if ripgrep had a slightly more advanced preprocessing API - allow returning multiple "files" per filename input, maybe even with a "sourcemap" of line<->Page etc.
There's just a lot of polish that needs to be done, and converting portions of it appropriate API documentation. Unfortunately, I don't really have the bandwidth to mentor this at the moment. :-( However, with that said, one super useful thing you could do is try out libripgrep and then give feedback[1] on how it worked for you, and in particular, which things were hard to figure out.
Wow, this looks like a great resource. I'm not currently in the bay area, but this looks perfect otherwise. I'm going to look into this a bit more, thanks!
I tried it once as an experiment, after a friend of mine suggested I, "just take it easy for once."
After that experiment, I hear any similar question as, "Would you consider working for less than half of what you make now, for someone who doesn't know how to manage a group of people?"
I do get a lot of executive headhunters in my inbox, and clients tender a lot of offers as well, but nothing remotely competitive nor interesting has yet come my way.
