[yellow_lead]

Unfortunately I lost trust in GitHub search a while ago. Can't find files, can't find an exact string reference. This can be dangerous in certain situations like you said. Hopefully I can start to gain trust in the new version when released but I don't really see myself using it again.

[prepend]

Same here. GitHub search sucks for authoritative, governance use cases. I got burned a few times and now just pull everything down myself and search it.

I think there’s code search companies but they are too expensive for me and I suppose some people really value it more highly.

Comically, I need the old Google search appliance and just treat it as a web source for lots of my questions (who is using log4j, etc).

[wahern]

> I need the old Google search appliance

Or Google Code Search! Which turned out to be Russ Cox's platform for developing RE2.

Google Code Search was simply amazing. Killing Google Code Search really underlined how Google had given up on it's pro-social agenda. I mean, here was a best-in-class and as yet unmatched service, neatly tailored to both the needs of developers and to Google's expertise and operations, and they killed it. Why? Because it wasn't going to make any money? Was there ever an expectation that it would?

The death of Google Books, when they removed countless scanned items, most of which were clearly out of copyright, was also painful. But I could understand how dealing with the barrage of copyright lawsuits was simply a bridge too far for Google. But Code Search? Why, oh, why!? :(

[mrslave]

> just pull everything down myself and search it.

`grep -r` or `git-all grep` or something better?

[yellow_lead]

I'm not who you replied to but I use ag and it's pretty fast (faster than grep I think)

https://github.com/ggreer/the_silver_searcher