Oni was/is build completely on top of neovim and oni2 turned vim (not neovim) into a library and builds on top of that.
I suppose the vscode plugin support is implemented in similar fashion as coc[1] does it.
I suppose the vscode plugin support is implemented in similar fashion as coc[1] does it.
The extension host is larger than just handling language services - it handles additional functionality, like source control, menus, language configuration - the full protocol is defined here: https://github.com/microsoft/vscode/blob/master/src/vs/workb...
We aim to integrate with that back-end extension host process - in other words, to support the `vscode` extension API surface, not just language support.
Because of the ubiquity and popularity of VSCode - the extensions tend to have significant investment and be of very high-quality, so we'd like to be able to leverage that wholesale.