[sqs]

Sourcegraph CEO here. The Sourcegraph Editor features (on https://about.sourcegraph.com/products/editor, plus other things on the roadmap that aren't on that page) are currently not possible to build as an extension.

One of two things will happen, assuming we build a great product (which is obviously our intent :):

1. We will prove that these features are valuable, and VS Code and other editors will eventually add support (or extensibility) for them. Then we could just ship extensions. Everyone wins. And our customers and business do well because we have a great server product for companies needing to scale up code intelligence and code reviews beyond what can run locally—the backend for all these editors that now support these new code intelligence and review features.

2. We'll prove these features are valuable, but other editors don't add them (or the extensibility to support them). Then we'll continue shipping a first-class standalone editor with support for these features, and developers who need these features will use that editor. The world will have one additional editor. For developers that don't use that editor, we'll build lightweight extensions for other editors with some of the functionality (and that make it easy to jump to our app from other editors).

I don't know which will come true, but I do know that either way, we as a company need to demonstrate that these things are valuable to developers in their editor. That's what we're focused on now. :)

[heroprotagonist]

This is good, I do not want this as a VSCode extension because I do not use VSCode. If you could build it right into Jetbrains, though... maybe.

I would be concerned about how it would integrate and would probably still prefer a separate application instead of a docked or pull-out frame.

[ben_jones]

What are your thoughts on editor preferences for developers? If a company wanted to adopt Sourcegraph wouldn't they need to force all their devs to use the Sourcegraph editor? What if half of the team used Jetbrains and the other half VS Code?

[sqs]

We were worried about this initially, too. It turns out that the features are valuable enough that developers are willing to use Sourcegraph as a separate search and review tool even if they don't use it as their main editor. So you can use IntelliJ for day-to-day editing and Sourcegraph for code review and search.

Perhaps we should make that explicit: "Whether you use it as your primary editor or just for searching and reviewing code, ..."

[ben_jones]

Thanks for the reply. The form factor for code-review and commenting were standout features for me and i'll definitely check out the process.

[sqs]

Also, you can set up Sourcegraph Server (https://about.sourcegraph.com/products/server) and then everyone gets the core features on all your company's code in their web browser.