I was always bummed OniVim v2 didn't take off.

It was a native IDE but fully supported VS Code plugin system.

https://web.archive.org/web/20210627210456/https://v2.onivim...

From a quick glance, I can't understand the target audience.

Vim users would be annoyed by bizarre input lag of an electron application and perhaps by EULA. VS code users don't really care about Vim...

	▲	forgotpwd16 an hour ago \| parent [-]
		>of an electron application It isn't an Electron application, that's why GP said native. The EULA part though was probably a block to adoption. It uses Revery, a, made by OniVim's devs, cross-platform GUI framework (similar to Flutter but build on Reason/OCaml).

▲

arbitrandomuser 3 hours ago | parent | prev [-]

onivim also seperated the core functionality of the vim editor into a seperate library libvim , this would have been great for other people looking to make their own gui frontend to vim .

neovim does not give a libneovim, but exposes an rpc where you communicate with neovim running as another process, this I would have thought have more latency but apparently is fast enough , this is how the vscode plugin for neovim is able to provide a near complete vim experience. Other neovim guis like neovide use this too