I've used the "first" (?) version of Sourcegraph and now this new one, and I have to say I'm a huge fan. I'm learning Go in the evenings and I was struggling to grasp some of the concepts in Go and how to use the Gorilla package. Personally, I learn better after I skim the API, look at an example and rinse/repeat as needed. For me, Sourcegraph is a great way to help speed up that process of finding that one example that helps make whatever it is "click".
I've been using their Chrome Extension because it injects their stuff right onto Github pages. Now all they need to do is make one for Firefox, so I can go back to Firefox.
Disclaimer: I meet Quinn at GopherCon and we talked about Sourcegraph. I loved the idea then, and I still do now.
This looks very nice; automated access to and analysis of the huge amounts of source code on the Internet could be a game changer for programmers everywhere.
As an aside, when I saw Google in the URL I thought that this was a rebranding of Steve Yegge's "Grok"[0] project. Does anyone know what's happened to that?
Oh, thanks for posting this! I'm the author (and one of the co-creators of Sourcegraph at https://sourcegraph.com), and I'm happy to answer any questions anyone has here.
We chose Go because it offers amazing facilities for introspecting its own source code, such as go/doc (http://golang.org/pkg/go/doc/ and https://sourcegraph.com/code.google.com/p/go/.GoPackage/go/d...) and go/types. So, it was the obvious choice to use to prototype Sourcegraph. The reputation of the core team and our initial experience learning it were also factors.
I've been using their Chrome Extension because it injects their stuff right onto Github pages. Now all they need to do is make one for Firefox, so I can go back to Firefox.
Disclaimer: I meet Quinn at GopherCon and we talked about Sourcegraph. I loved the idea then, and I still do now.