[1] https://sourcegraph.com/github.com/joyent/node/.CommonJSPack...
I've tried Sourcegraph and think it solves a real pain point but I have had problems integrating it into my workflow. I'm not sure when I should be using it. I've been meaning to use it to read more open source code code but it seems like they recently disabled support for Ruby.
Some examples:
https://www.omniref.com/ruby/2.1.2/symbols/Enumerable/sort_b...
https://www.omniref.com/ruby/gems/sass/3.3.8
https://www.omniref.com/ruby/2.1.2/symbols/MiniTest
https://www.omniref.com/ruby/gems/activerecord/4.1.1/symbols...
You can even build custom search engines for your project by uploading your project's Gemfile.
We will have Ruby support back in soon, hopefully this week. I'll email you when it's in to get your feedback.
As for integrating it into your workflow, the new improvements we pushed today make it much faster and easier to use Sourcegraph to find docs and examples. In a lot of cases, Sourcegraph will give you the docs or examples you want faster than a Google search. (And often Sourcegraph , because it actually analyzes code, will have examples that you can't find anywhere else.)
But we still have a lot of work to do, and it'd be great to hear your feedback on when Sourcegraph works well for you and when it doesn't.
Other than that: cool tool! :-)
For example, "d3.timer" doesn't show meaningful results?
However, type inference on JavaScript is quite hard, and as you've seen, our analyzer fails on many complex libraries like d3. We have an open issue about fixing d3 support at https://github.com/sourcegraph/sourcegraph.com/issues/13, which you can +1 if you want to stay updated on. And we're releasing the analysis toolkit we use as open source soon so it's not bottlenecked on us.
It looks awesome. Bravo.
(I'm the co-creator of Sourcegraph.)