CodeEdit vs Neovim
CodeEdit
codeedit.appNeovim
neovim.ioSide by side
| Figure | CodeEdit | Neovim |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | — |
| Windows | — | Yes |
| macOS | Yes | Yes |
| Linux | — | Yes |
| Android | — | Yes |
| API | — | Yes |
| Self-hosted | — | Yes |
| Plans published | 1 | 1 |
| Spec score · Code editors | 7.8 (#32) | 9.0 (#3) |
| Community support | The project invites users to join its Discord and GitHub Discussions to discuss and collaborate on CodeEdit. | Users can ask questions through GitHub Discussions or vi.stackexchange.com and chat on Matrix or IRC. |
| Extension support | Yes | Yes |
| Free plan | Yes | Yes |
| License | The repository says CodeEdit is licensed under the MIT license. | Neovim is licensed under Apache 2.0 except for parts contributed under the Vim license. |
| Product | CodeEdit is a code editor written for macOS. | Neovim is a Vim-based text editor engineered for extensibility and usability. |
Plans
In their own words
Neovim
Neovim is a free, Vim-based text editor built for extensibility and usability. It keeps Vim’s editing model and Vimscript v1 support, while configuration lives in init.lua and users can create Lua plugins. Its documented, versioned API and RPC let developers build extensions in many languages; GUIs, IDEs, and web browsers can also embed Neovim. Tree-sitter supports syntax highlighting and text objects, and built-in language-server support provides semantic code inspection and refactoring. Editing tools include multicursor command replay, macro recording, column editing, and large-file handling. A built-in terminal includes modern terminal features. Neovim supports Vim 8.x plugins and more. Stable downloads are listed for Linux, macOS, and Windows, with x86_64 and arm64 builds for each. Windows 8 or newer is required; Windows 7 and older are unsupported. It is licensed under Apache 2.0, with exceptions for parts contributed under the Vim license. Community support is available through GitHub Discussions and vi.stackexchange.com.