The Sourcegraph Editor is a fork of vscode? Is it not possible to implement it with an extension? Happily would install an extension but i'm not sure whether i would switch the editor
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. :)
Perhaps we should make that explicit: "Whether you use it as your primary editor or just for searching and reviewing code, ..."
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.