"But they didn't go through and parse the code like we do. It couldn't tell you who else uses this particular function or repository."
It may have, but perhaps didn't present the UI for external users. Our internal version of Codesearch based on Grok (http://www.stanford.edu/class/ee380/Abstracts/121010.html) is far more powerful and works just like an advanced IDE -> find usages, callers, implementors, overrides, all kinds of auditing/analysis layers too.
Some Googlers practically live in Codesearch rather than use the local IDE indexing :)
As someone stuck with CScope on Linux, I really really wish there were better alternatives for the wider world. (required features: works with C, query from terminal as well as from IDE (inc. Vim/Emacs), possibility to jump to func/type definition as well as callers/users)
Codesearch is probably the largest reason I am jealous of my friends at Google.
It may have, but perhaps didn't present the UI for external users. Our internal version of Codesearch based on Grok (http://www.stanford.edu/class/ee380/Abstracts/121010.html) is far more powerful and works just like an advanced IDE -> find usages, callers, implementors, overrides, all kinds of auditing/analysis layers too.
Some Googlers practically live in Codesearch rather than use the local IDE indexing :)