Sourcegraph co-creator here. Thanks for posting this! We pushed a bunch of improvements to Sourcegraph to make it faster and easier for you all to search for code and find real usage examples (taken from other projects on GitHub). We’re developers, too, and we want Sourcegraph to be the developer reference tool we want to use 100x a day. Let me know if you have any feedback. :)
It’s looking swankier and swankier every time I check it, great work!
I noticed the golang crawling has some bugs in it though:
In the side nav, the dependents count is often incorrect, for example: https://sourcegraph.com/github.com/go-yaml/yaml/.dependents
Traversing dependencies links are sometimes broken, for example: https://sourcegraph.com/github.com/go-yaml/yaml/.dependencies -> https://sourcegraph.com/gopkg.in/yaml.v1
Searching for gopkg.in modules does not work, for example: gopkg.in/yaml.v1
gopkg.in-wrapped dependencies are not recognized (that may be asking for a lot, but would be very handy, especially if they got merged under the parent package unlike http://godoc.org/gopkg.in/yaml.v1?importers which keeps them separate.)
In general, the results seem to be quite different from godoc.org, for example: http://godoc.org/github.com/go-yaml/yaml?importers
From the scenarios where Sourcegraph did work, I found it very handy. If most of the above was fixed, I can see myself growing fairly dependent on the service. :)
Thanks, this feedback is super useful!
I filed bugs on us for points 1-4: https://github.com/sourcegraph/sourcegraph.com/issues/161 and https://github.com/sourcegraph/sourcegraph.com/issues/162.
As for having different results from godoc.org, yeah, there are a lot of improvements we could make there. In the case of that link you posted, it looks like both Sourcegraph and godoc.org each had 1 importer/dependent but they were different. I just triggered a build of the one godoc was showing, and now Sourcegraph has both. Of course, in many cases Sourcegraph will be worse than godoc.org–but we’re working really hard to improve it all the time.
Please keep the feedback coming!
I was expecting to get something back for sys.exit as it mentions python but I don’t get any results back.
We just pushed an improvement to make it get Python C definitions better (of which sys.exit is one). Expect a blog post announcement soon.