This looks really cool and is one feature that I think is missing from Dash. There are tons of integrations for editors with Dash and its a great resource to be able to quickly look up documentation when you need it but its definitely missing a curated set of examples depending on the documentation you’re looking at, i’ve found most documentation that I use at least is pretty void of usage examples. This means generally if i want to find how its used I’ll need to go over to Google to search for actual usages.
I like the way Dash does the integration better than having an always on window that updates while I type, personally I would get really distracted seeing the right side of my screen always flickering with new information.
Sourcegrapher here. Thanks for the kind words. We built this editor integration because we 100% agree with you—actual usage examples are super valuable.
You can turn off the live-updating, always-on behavior in the editor plugin. See https://github.com/sourcegraph/sourcegraph-vim#vimrc or https://github.com/sourcegraph/sourcegraph-sublime#auto. Then you just use a hotkey to jump to usage examples. Or you can just keep that browser window in the background (that’s how I use it, since I use a full-screen WM on Linux).
I don’t know that I would call this automatic pair programming. It looks cool and sounds useful, but most of the time I’ve spent pairing hasn’t been looking up documentation while someone else writes the actual code or vice versa.
Outside of actual utility or quibbling over the title, I would be concerned about using this because it is leaking a lot of stuff to an external service.
Yeah, we tried to make it send the absolute minimum amount of data to an external service. It doesn’t send the code files, only the resolved tokens' package (Go import path), repo name, and definition path (e.g. “FuncName” or “TypeName/MethodName”). More info in the editor plugin readmes at https://github.com/sourcegraph/sourcegraph-sublime and https://github.com/sourcegraph/sourcegraph-vim. Some folks indeed won’t be able to use it because of their company’s policy, so we’re just trying to do the best we can to be transparent and conservative here.