[meekins]

It's interesting that the #2 selling point on the landing page (the Copilot integration) relies purely on Microsoft's goodwill. There is no official API for Copilot but instead a (non-standard) LSP implementation embedded into the proprietary Copilot Neovim plugin. Zed seems to trust under the hood that a release of the plug-in exists on Github, pulls the minified-js language server from there and integrates with that. The minute MS decides to pull the plug on the Neovim plugin Zed loses the functionality as well.

I wish we had a proper API to interact with copilot but it seem that pulling everyone else except the dedicated VIM and JetBrains users into VSCode land seems to be more in their interest.

[impulser_]

Why would Microsoft pull Copilot from Neovim?

Microsoft doesn't care if you use copilot with VSCode or not. Copilot is a paid product the more support the better for them.

I bet Microsoft doesn't care if you use VSCode or not. It's not a paid product.

[nicce]

It is not paid product for non-commercial and open-source products. The get massive amount of data if you use it in VSCode, and because of this, it is pain to ass to use on VSCodium for example. Your data is the currency, and other editors are good on limitin that.

[meekins]

If they wanted non-sanctioned editors integrating Copilot they wouldn't have taken the extra steps of implementing an obfuscated LSP but provided an API or a plain client library. At best this could be a pet project by a Neovim fan GH employee. Either way I wouldn't expect long term (if any) support from this thing.

[alberth]

> the Copilot integration) relies purely on Microsoft's goodwill

Given that the founders and several employees are former GitHub employees, I have to imagine they know how to do this integration in a proper & officially allowed way.

https://zed.dev/team