51–60 of 95 posts
Based on your caret position, it would automatically show you crawled examples of how other people use the functions/classes you are dealing with.
Has that been de-emphasised or gone away?
Hard pass. I dont want an "intelligent" search I just want a search. Will be sticking with Agent Ransack.
There is "code intelligence", which is a phrase we use to describe IDE-like features such as jump-to-definition, find-references, etc.
The kind of cross-reference SourceGraph provides is a must have for me after a few years of using a tool like it to understand big projects (I don't use SourceGraph, I use Grok/CodeSearch). Google open sourced a version of Grok some time ago ( https://kythe.io/ ). [1] A quick search also found this `OpenGrok` thing which I assume must be yet another generic indexer [2]. I wonder if there are other popular tools out t…
Some comparisons based on my reading so far: Adding a language: Kythe: a language implementation provides some structured graph SourceGraph: a language implementation is an LSP server Backend logic: Kythe: has common logic for querying for relationships SourceGraph: simply proxies LSP requests through to the appropriate language server. Terminology: Kythe: An indexer is a language implementation SourceGraph: The inde…
We ended up switching away from that model for a few reasons:
- At the time it was very costly to essentially index the whole OSS world, when most commit indexes would never be read.
- It was slow to index a codebase for a commit, and most of the work was wasted since a developer would often only look at a handful of files.
- Getting incremental indexing working usually required pretty deep integration into the build tool, so was a lot of work per language which didn't scale.
- A lot of tools using an "indexed" model end up only indexing the master/trunk branch, and you don't get your code intelligence features for PRs/etc.
At some point LSP came onto the scene. We were early adopters making a bet that this would take off. It has, and the list of community created LSP servers is large: https://langserver.org/ It also allowed us to switch from an upfront indexing model, to a model which just encodes user intent. So the underlying LSP server can be as lazy as it wants to be with respect to how it responds to the user == increased perf and reduced resources.
Things like cross-repo references doesn't come with LSP. Many LSP servers assume the user sets the build up correctly. There are also quite a few more assumptions LSP authors make which don't easily translate into an automated server environment. So we have done quite a bit of work to smooth that over / contributed some LSP servers for popular languages.
Seems like you are digging in so you might have more questions. I'll try keep track of this thread, but also feel free to email me keegan at sourcegraph.com or file issues/questions on our repo.
Earlier quoted context omitted.
Hey, couple questions for you: - We are a pretty small shop, only 3 developers, and looking at Sourcegraph for the first time. We have a full Kubernetes cluster for running some of our production applications and would be happy to run this there. The Sourcegraph site lists a Quickstart instructions and instructions for Data Center. I am unsure what exactly the difference between them is. - The Docker image for source…
You should definitely use our Quickstart instructions :) You can deploy it to your existing Kubernetes cluster (or any other Docker environment). - The Quickstart instructions[1] describe how to set up a single-machine single-container Sourcegraph instance, which is recommended for small teams. Our Data Center[2] offering is for large teams and runs Sourcegraph across multiple machines in multiple containers for high…
I remember Sourcegraph as being a sort of sidecar to your text editor. Based on your caret position, it would automatically show you crawled examples of how other people use the functions/classes you are dealing with. Has that been de-emphasised or gone away?
With Sourcegraph, we have editor plugins for various editors[2] but they only perform "Open current file on Sourcegraph" and "Search selection on Sourcegraph" actions, nothing like what you are describing yet.
[2] https://about.sourcegraph.com/docs/integrations/editor-plugi...
Sourcegraph CEO here. We're back to work on testing release candidates for Sourcegraph 2.12, coming out this week. I'm especially excited about a few big new features that fit really nicely into the code search and browsing workflows people use Sourcegraph for: - https://github.com/sourcegraph/about/blob/master/projects/ex... - https://github.com/sourcegraph/about/blob/master/projects/so... - https://about.sourcegrap…
Earlier quoted context omitted.
I tend to agree, although I probably wouldn't state it in exactly the way you have. Open core's main goal is to sell proprietary software using the open source version as a loss leader. Having said that, I think there are some companies/individuals who truly believe that open core is a good way of funding free software development. I have even heard Bruce Parens claim that dual licensing is practically the only reaso…
Sourcegraph CEO here. I share your interest in open-source business models, going back quite a while. My public middle school back in 1999 had a mock investment club, and students voted on which stocks to invest in. (It's funny looking back on this.) I campaigned for RedHat and VA Linux, and we ended up "buying" those (and some JDS Uniphase, naturally). I plan to write more about this, but here's the summary of why w…
As a complete aside, I actually had inside knowledge of the JDS - Uniphase merger (a friend of mine who worked there inadvertently allowed me to see something that made it was clear that it was happening a day or so before). It took all my self control not to buy up a lot of JDS stock. I always wonder if I would have gotten in trouble (or gotten my friend in trouble)...
Earlier quoted context omitted.
Cool! Are you working on IDE plygins, e.g. for Atom?
Yes, we have basic editor/IDE plugins that let you (1) open up Sourcegraph to the current document's file/line and (2) search. Sourcegraph for Atom is in prelrease at https://github.com/sourcegraph/sourcegraph-atom . Other editors are at https://about.sourcegraph.com/docs/integrations/ . What features (other features, if any) are you specifically interested in? It would be awesome if you posted feature request issues…
The two most popular editors used by programmers...
Sigh