Neovim

Neovim exists to refactor Vim aggressively. The stated goals are simplifying maintenance, encouraging contributions, splitting work across multiple developers, and letting advanced user interfaces be built without modifying the core editor.

Most of that leverage comes from the API, which any language can drive. The project lists clients written in C, C++, C#, Clojure, D, Elixir, Go, Haskell, Java, Kotlin, JavaScript, Julia, Lisp, Lua, Perl, Python, Racket, Ruby and Rust.

The editor adds a handful of things on top of Vim.

• Modern GUIs: separate front ends talk to one core over the API.
• Terminal emulator: embedded and scriptable, running inside the editor.
• Asynchronous job control: long running work does not block your editing.
• Shared data: a shada file carries state between multiple editor instances.
• XDG base directories: configuration lands where the specification says it should.

Compatibility stayed deliberately wide. Most Vim plugins still work, Ruby and Python ones included, and a dedicated help topic walks through what changes when you move across from Vim.

Contributions after a marked commit carry the Apache 2.0 license, except for code copied from Vim, which keeps its original terms. Builds use CMake with a Makefile wrapper for convenience, and pre built packages cover Windows, macOS and Linux, alongside managed packages in Homebrew, Debian, Ubuntu, Fedora, Arch Linux, Void Linux and Gentoo.