Sourcegraph Master Plan
about.sourcegraph.com
Sourcegraph Master Plan
1–10 of 37 posts
Re: Sourcegraph Master Plan
#2Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions!
Re: Sourcegraph Master Plan
#3[deleted]
Re: Sourcegraph Master Plan
#4Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions!
[deleted]
Re: Sourcegraph Master Plan
#5Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions!
Looks awesome and I hope to hear from succeed!
The blue box half way down is really bad on mobile. Too much margin.
Re: Sourcegraph Master Plan
#6I don't get what problem this solves that Emacs with appropriate language modes doesn't already solve.
Re: Sourcegraph Master Plan
#7I don't get what problem this solves that Emacs with appropriate language modes doesn't already solve.
People use a lot of different editors. The solution isn't "everyone switch to emacs".
Re: Sourcegraph Master Plan
#8Sourcegraph CEO here. Thanks for posting this. Happy to answer any questions!
How much of this plan do you envision will be provided by Sourcegraph and how much comes from the many other people working on similar things? (For example, many people are working on language servers these days.)
Re: Sourcegraph Master Plan
#9Isn't Kythe[0] trying to achieve this already, with a graph based, multi-language framework?
Of course, there are no integration with current dev tools, but the core is there to make it work, maybe?
[0] - https://kythe.io
Re: Sourcegraph Master Plan
#10Isn't Kythe[0] trying to achieve this already, with a graph based, multi-language framework? Of course, there are no integration with current dev tools, but the core is there to make it work, maybe? [0] - https://kythe.io
Sourcegraph CEO here. Yes, Kythe is a very ambitious project and we have a lot of respect for the team building it inside Google. source{d} (https://sourced.tech/) is another company doing awesome things in the code analysis space.
From our POV, the more people trying to accomplish these things, the better, because:
1. As developers and humans, we want these things to exist!
2. Our business and product is a code search and browsing tool, which benefits from better code intelligence/analysis. We don't sell language servers directly; we sell a tool that makes use of them.
(For interactive tools (editors, code search, and code browsers), which is what we're primarily targeting, LSP (https://microsoft.github.io/language-server-protocol/) is a better fit than Kythe.)