Helix adoption shifts terminal editing focus

The selection-first paradigm

Helix uses a selection-then-action paradigm. This approach differs from Neovim, which follows an action-then-object model. In Neovim, users specify a command like delete and then a target like word. In Helix, users first select the word and then apply the delete command. This method prevents mistakes. You, who prefer simplicity, might find the TOML configuration refreshing.

Neovim relies on a large collection of Lua plugins for tasks like fuzzy searching, treesitter, and LSP. Users often manage plugin managers like lazy.nvim or configure distributions like AstroNvim. Helix ships with these tools built in. It includes a fuzzy file picker, autocompletion, multi-cursor support, and terminal integration. Helix also contains minor modes like Goto, Match, View, and Space. Space mode provides mappings to a fuzzy file picker, a buffer picker, a jumplist picker, and a symbol picker. These tools exist without external plugins. In Neovim, the user must use a plugin like whichkey.nvim to achieve a similar experience to Helix Space mode. In Neovim, a user might type di{ to delete inside braces, where d is the action and i{ is the selection. The Helix model requires users to select the word before applying the delete command. This pattern ensures the user sees the target before the action occurs. Neovim utilizes C for its core, supplemented by Lua and Vimscript. Helix uses Rust, a language that emphasizes safety and memory-correct programs. The software remains highly efficient.

Neovim handles more language servers through the nvim-lspconfig plugin and the selection model reduces errors.

Helix uses TOML for configuration.

Version 25.07 technical improvements

The 25.07 release replaced the old Tree-sitter integration with a new crate called Tree-house. Tree-house handles injections more effectively, such as highlighting code within Markdown blocks. It also improves incremental injections. This change solves maintenance issues found in the previous highlighter. Tree-house uses a layer concept where the root layer covers the document and child layers cover injections. This allows for deeply nested injections, such as Markdown inside Rust doc comments.

Developers see color swatches inline thanks to new LSP document color requests. This functionality shows RGB colors directly in the editor. The 25.07 release also added a file explorer under the space and e key. This picker allows users to move through directories as a hierarchy. Users who select a directory with Enter open a new file explorer under that directory.

Command mode received a complete rewrite. This rewrite adds flags and expansions to the command line. Users can now use flags like –no-format for the write command or –reverse for the sort command. Expansions allow users to insert variables like %{buffer_name} or %{cursor_line} into commands. The rewrite also fixes bugs in parsing and completion. Command mode avoids "quote hell" by using serde_json to parse complex configuration values. Users can run shell commands using the %sh expansion.

Does a lack of a plugin system limit Helix users?

Ecosystem and performance realities

Neovim reaches a wide user base through its long history and large plugin repository. GitHub data from April 2026 shows Neovim holds 102,000 stars. Vim holds 40,000 stars. Neovim users often use Lua to build advanced extensions. The r/neovim subreddit has 180,000 members, while r/vim has 130,000 members. A Stack Overflow survey from 2025 shows Neovim at 12% and Vim at 13% usage. Combined usage for both reaches 38.3% of developers. This adoption includes developers using Neovim for writing commit messages or simple configuration edits.

Helix provides stability through minimal configuration. It lacks a plugin infrastructure for now. Development of a WebAssembly-based system continues. Most users prefer the convenience of built-in tools. Neovim 0.12.5 stands as the current stable release. Vim 9.2.1025 remains the latest version for the Vim project.

Both editors run fast. Helix runs fast. Neovim experiences delays when loading many plugins.

One developer manages sessions with tmux while using Helix for code editing. This developer uses Ghostty as a terminal emulator and lazygit for git operations. This developer also uses Claude Code in a separate tmux window. When Claude Code modifies a file in another tmux window, the developer presses the Ctrl+r key combination to refresh all active buffers and ensures the editor updates every single line of code instantly.