5 ms·

Sourcegraph CEO here. Congrats to the Kite team! As a desktop Linux user (Ubuntu and ChromeOS), I am excited to see this. How are you managing the maintenance

by sqs 7y ago

Sourcegraph CEO here. Congrats to the Kite team! As a desktop Linux user (Ubuntu and ChromeOS), I am excited to see this. How are you managing the maintenance of multiple editor extensions? Do you use some kind of architecture where there is a common background process with most of the logic and a simple adapter per-editor? How many people on your team are actually writing code against editor extension APIs?

adamsmith 7y ago
Yes we use a headless process that the editor plugins talk to. Our heads-up-display app also talks to this headless process. We put as much functionality there as possible and try to keep the plugins/HUD as small as possible. It’s still a challenge with this approach. We have to be careful what new surface area we add to plugins, and have rolled back editor features that users don’t engage with. We also keep the API well documented and have a detailed product spec that the editors try to adhere to. The product spec can be challenging because each editor API supports slightly different types of interactions. So after all of these strategies the main thing making it work is the team!