3 ms·
Nice. Is the code search the same as what Google has internally? I do miss that. (Though honestly, the value from the internal code search was that everythin
by jrockway 8y ago
Nice. Is the code search the same as what Google has internally? I do miss that.
(Though honestly, the value from the internal code search was that everything was in there. So if you got an error message from a service you were a client of, you could just search for the error message in their code and see what it actually meant. "Aha, this 'optional' field that's marked 'deprecated' isn't actually optional or deprecated," most of the time ;)
- duality 8y agoYou might also want to check out https://kythe.io https://kythe.io and https://github.com/google/kythe https://github.com/google/kythe.
- romed 8y agoIt’s great that they opened Kythe but as someone who deployed it from scratch I say it’s like ordering a DIY aircraft carrier kit. Many steps before you get something useful.
- romed 8y agoHaving glanced at it a bit I don’t see how this can be based on internal code search / kythe. Kythe works by building your codes. That’s how it can find callers and specializations and whatnot. This doesn’t seem to.
- lallysingh 8y ago"It looks for matches by file names, classes, functions and other symbols, and matches the context and namespace of the symbols" Correct. Looks like it just parses and indexes the source.
- russellwolf 8y agoAuthor of the blog post here. The code search functionality is the same as what Google engineers use internally. Cloud Source Repositories uses the same indexing and retrieval technologies on the same type of infrastructure. As you mention, the more code you have, the more benefit you get from having fast search tools across your entire code base that can perform complex semantic and regular expression queries. Even with smaller codebases, I find it the fastest way to find the code I need. (Disclaimer: I work at Google and am the PM on this product)