4 ms·

Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions here. We're really excited to start helping with the code editing and review workfl

by sqs 9y ago

Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions here. We're really excited to start helping with the code editing and review workflow as well.

euyyn 9y ago
Hi! Big fan of your work here. My question is: What do you think about Kythe, the open-source version of Google's Grok (https://github.com/google/kythe https://github.com/google/kythe)? In the context of both your overall vision, and of strategies: Do you do things similarly? Do you see collaboration/integration there as desirable?
- sqs 9y ago
  That's a good question. They've built an amazing system. Google and ex-Google engineers love the code intelligence/search systems that Google has, and those are powered by Kythe and related systems inside Google. At a product level, many ex-Googlers miss those systems in their new companies and fill the gap by setting up Sourcegraph internally. Tech-wise, Kythe is optimized for offline analysis, and we use servers that speak LSP (https://github.com/Microsoft/language-server-protocol https://github.com/Microsoft/language-server-protocol), which is built for online analysis and use while you're editing code. That is what I see as the main difference. We would love for the approaches to converge, or for the representation/configuration to be compatible.
  - Sophistifunk 9y ago
    I think online analysis is the way to go, for those of us using non-google-sized codebases. Of the many tools I feel programmers are missing in order to clean up the mess we're making, Sourcegraph is trending towards several of them - keep up the good work!
boyter 9y ago
Sourcecode server? Can I take some credit for the name :P Looking forward to trying it out. What’s the response to the single search box so far? I quite like it but one of the reasons I have never implemented one for searchcode is that the vast majority of users were confused by it when I tested it with them.
- arikr 9y ago
  > Sourcecode server? Can I take some credit for the name :P I realize you're semi-joking, but wanted to note that I don't think it's a particularly original/unique/secret name
  - boyter 9y ago
    Totally joking. The sourcegraph guys know who I am and I bear them no ill will. That said I do run searchcode and the downloadable version is named searchcode server (launched a year ago) hence the joke about the name.
    - sqs 9y ago
      Ha ha. I liked it. You'll need to call your editor the Boyditor.
shredfg 9y ago
I love the product myself a lot. I am currently a student who tries to contribute large open source stuff and been using it to track code for a few months.
- sqs 9y ago
  Glad to hear that!

by sqs 9y ago

Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions here. We're really excited to start helping with the code editing and review workflow as well.

euyyn 9y ago

Hi! Big fan of your work here. My question is: What do you think about Kythe, the open-source version of Google's Grok (https://github.com/google/kythe https://github.com/google/kythe)? In the context of both your overall vision, and of strategies: Do you do things similarly? Do you see collaboration/integration there as desirable?

sqs 9y ago
That's a good question. They've built an amazing system. Google and ex-Google engineers love the code intelligence/search systems that Google has, and those are powered by Kythe and related systems inside Google. At a product level, many ex-Googlers miss those systems in their new companies and fill the gap by setting up Sourcegraph internally. Tech-wise, Kythe is optimized for offline analysis, and we use servers that speak LSP (https://github.com/Microsoft/language-server-protocol https://github.com/Microsoft/language-server-protocol), which is built for online analysis and use while you're editing code. That is what I see as the main difference. We would love for the approaches to converge, or for the representation/configuration to be compatible.
- Sophistifunk 9y ago
  I think online analysis is the way to go, for those of us using non-google-sized codebases. Of the many tools I feel programmers are missing in order to clean up the mess we're making, Sourcegraph is trending towards several of them - keep up the good work!

boyter 9y ago

Sourcecode server? Can I take some credit for the name :P Looking forward to trying it out. What’s the response to the single search box so far? I quite like it but one of the reasons I have never implemented one for searchcode is that the vast majority of users were confused by it when I tested it with them.

arikr 9y ago
> Sourcecode server? Can I take some credit for the name :P I realize you're semi-joking, but wanted to note that I don't think it's a particularly original/unique/secret name
- boyter 9y ago
  Totally joking. The sourcegraph guys know who I am and I bear them no ill will. That said I do run searchcode and the downloadable version is named searchcode server (launched a year ago) hence the joke about the name.
  - sqs 9y ago
    Ha ha. I liked it. You'll need to call your editor the Boyditor.

shredfg 9y ago

I love the product myself a lot. I am currently a student who tries to contribute large open source stuff and been using it to track code for a few months.

sqs 9y ago
Glad to hear that!