> NeoVim seems like a bit of a waste to me, because I think it misses the point. Vim is not a platform.
Neovim is designed to be hosted (embedded). Embedding Neovim in a IDE (platform) allows Neovim to be the editor while exposing the IDE as "the platform".
It's also a guiding principle of Neovim to not dictate what applications are built with it, so yes, you can leverage its API as a platform. But that's not the singular purpose.
> I guess what I mean is that vim should be left as vim. There are superior platforms that implement the same interface,
There are no applications that implement Vim (except Neovim, which passes Vim's test suite).
What's the process of embedding neovim into something like xcode? the thing that always got me confused is how the IDE would handle the text changing on an open file like that. What's the flow expected to be?
I'm guessing some kind of event system out of band that the IDE can hook into. Using the OS for that is probably too low level to provide the experience people expect. https://neovim.io/doc/user/msgpack_rpc.html
Neovim is designed to be hosted (embedded). Embedding Neovim in a IDE (platform) allows Neovim to be the editor while exposing the IDE as "the platform".
It's also a guiding principle of Neovim to not dictate what applications are built with it, so yes, you can leverage its API as a platform. But that's not the singular purpose.
> I guess what I mean is that vim should be left as vim. There are superior platforms that implement the same interface,
There are no applications that implement Vim (except Neovim, which passes Vim's test suite).