Neovim
Hacker ApprovedRanked 5 of 56 text editors by recommenders
A keyboard-driven, extensible Vim fork with built-in LSP, Lua scripting and a strong plugin ecosystem, though critics cite breaking changes and an upgrade that deleted old Vim undo files.
A keyboard-driven, extensible Vim fork with built-in LSP, Lua scripting and a strong plugin ecosystem, though critics cite breaking changes and an upgrade that deleted old Vim undo files.
406 people gave an opinion
- recommend it
- 295
- criticize it
- 111
- approval share
- 73%
Recommended in 12 of 13 months
- November 2025: recommended
- December 2025: recommended
- January 2026: recommended
- February 2026: recommended
- March 2026: recommended
- April 2026: recommended
- May 2026: recommended
- June 2026: recommended
- July 2026: recommended
- August 2026: recommended
- September 2026: recommended
- October 2026: recommended
- November 2026: not recommended (month in progress)
Owned for 6 years
Median of the 20 owners who said how long they have had it.
Each square is one year.
Why it carries the badge
- 295 people recommend itNeeds 10 or more, met.
- 2.7 recommenders for every criticNeeds 2 to 1 or better, met.
- Recommended in 12 of 13 monthsNeeds 4 or more, met.
The same three rules apply to every product, and the badge can’t be bought. How the badge works
What people say about it
The reasons people give, with the number of comments that give each one. Open a reason to read what they said.
Why people recommend it
Each mark is one comment
Fully keyboard-driven workflow
“neovim on android/termux is actually easier to use than any of the IDE editor apps mainly due to everything being keyboard based”
Comment from 17 Mar 2026 in “Lazycut: A simple terminal video trimmer using FFmpeg” “I feel this is the superior paradigm: You don't even need to get to some specific location in order to edit it.”
Comment from 7 Mar 2026 in “Ki Editor - an editor that operates on the AST” “youre using the keyboard to do most things anyway, so the keyboard can just stay open all of the time”
Comment from 7 Jan 2026 in “Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone” - Comment from 30 Dec 2025 in “You Need to Ditch VS Code”
- Comment from 31 Jul 2026 in “Rune 1.1: adds Python, an Emacs editor, a symbol index and is now free”
Rich, extensible plugin ecosystem
“There is more flexibility to extend easily, to customise, to make my environment fit using these more”
Comment from 30 Dec 2025 in “You Need to Ditch VS Code” “a plugin you write for neovim can run in the terminal, in any Neovim GUI or in another application”
Comment from 12 Nov 2025 in “The terminal of the future” “navigating and selecting things SYNTACTICALLY with nvim-treesitter-textobjects is life-changing”
Comment from 16 Dec 2025 in “VS Code deactivates IntelliCode in favor of the paid Copilot” - Comment from 21 Feb 2026 in “Ask HN: Is it worth learning Vim in 2026?”
Native LSP and Lua scripting
“the main advantages over Vim are just the Lua scripting instead of Vimscript, its support for language servers”
Comment from 30 Mar 2026 in “Neovim 0.12.0” “With its own package manager now, and LSP library, you really don't need a lot of config tweaking”
Comment from 29 Mar 2026 in “Neovim 0.12.0” “moved to Neovim for other reasons, chiefly performance/LSP nativity/plugin ecosystem vitality”
Comment from 21 Feb 2026 in “Ask HN: Is it worth learning Vim in 2026?” Keeps you focused and productive
“I have found a huge productivity boost being able to stay in Neovim for extended periods of time”
Comment from 2 Jun 2026 in “strace-ui, Bonsai_term, and the TUI renaissance” “I mainly use (neo)vim because it has a less distracting interface than any other full blown IDE.”
Comment from 14 Mar 2026 in “Emacs and Vim in the Age of AI” “removing that micro-latency of "eye-to-mouse-to-tree" keeps you in the flow state much longer.”
Comment from 30 Dec 2025 in “You Need to Ditch VS Code”
What people warn about
Each mark is one comment
Upgrade deleted old undo files
“they did it in a completely stupid way and responded to a bug report about it in a way that suggested this might not be just the occasional stupid”
Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted” “That Neovim changed the default storage path for undo files is completely irrelevant to whether the contract for persistence should be broken.”
Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted” “It's not a good reason for just deleting the old undo file with no warning. All the new version needs to do is ignore it, not nuke it.”
Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted” - Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted”
- Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted”
- Comment from 28 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted”
- Comment from 28 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted”
- Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted”
Breaking changes and plugin churn
“I moved to neovim (stable) with as few extensions as possible, and those I've pinned to some geriatric version.”
Comment from 20 May 2026 in “GitHub Compromised” “No such thing exist in neovim (or at least in times when I was using it), so that churn never ends.”
Comment from 15 Jun 2026 in “Even More Batteries Included with Emacs” “There have also been multiple breaking changes over the last five years, including breaking compatibility with established default vim keybindings.”
Comment from 30 Mar 2026 in “Neovim 0.12.0” - Comment from 2 Jan 2026 in “Going immutable on macOS, using Nix-Darwin”
Limited built-in terminal output window
“instead of switching back from the alt screen and giving you your terminal back, they open a gimped little window within vim which makes it hard to navigate, copy, and search for things in the output”
Comment from 13 Nov 2025 in “Zed is our office” “It doesn't support interactive commands. For example if you run a command that asks for input before finishing, it gets swallowed.”
Comment from 27 Sep 2026 in “On caring for user data: NeoVim caused Vim undo files to be deleted”
Other text editors people recommend
The four most recommended other text editors, with the same counts for each, so you can compare like for like. The tick on each bar marks the 2 to 1 line the badge needs.
| Product | Recommend | Criticize | Approval | Months | Owned | Badge |
|---|---|---|---|---|---|---|
| Zed | 700 | 430 | 62% | 13 | 6 mo57 owners | — |
| GNU Emacs | 648 | 207 | 76% | 13 | 20 yrs158 owners | Approved |
| Vim | 513 | 127 | 80% | 13 | 20 yrs55 owners | Approved |
| Visual Studio Code | 485 | 547 | 47% | 12 | 2 yrs13 owners | — |
| Neovim | 295 | 111 | 73% | 12 | 6 yrs20 owners | Approved |
What people said
40 of the 542 comments that mention it, newest first. Each links to the original comment.
“I started experimenting with more traditional text editors since last spring and am happy to say, that I'm a happy user of Neovim now.”
“losing weeks' worth of work just because you deleted it recently by mistake and then upgraded with the app deleting the undo”
“Program that claims to be a drop-in replacement will arbitrarily delete data in ways that the program it replaces doesn't”
“That Neovim changed the default storage path for undo files is completely irrelevant to whether the contract for persistence should be broken.”
“It doesn't support interactive commands. For example if you run a command that asks for input before finishing, it gets swallowed.”
“It's not a good reason for just deleting the old undo file with no warning. All the new version needs to do is ignore it, not nuke it.”
“Neovim could have easily done both without the deletion. Willful negligence is morally very bad when it can cause user harm.”
“they did it in a completely stupid way and responded to a bug report about it in a way that suggested this might not be just the occasional stupid”
“How many neovim users were made aware that the software would proactively delete their decade-long file history?”
“This issue with Neovim sounds like less than ideal design, or a bug, or both, not some kind of intentional affront to users.”
“if the format of the persistent undo file is unstable, and Neovim just deletes it when it doesn't recognize the previous format”
“the entire editor and the plugin ecosystem is fully based on the same keyboard-driven workflow”
“The Neovim/LazyVim speed for writing code turns out to be just as fast for navigating and reviewing code.”
“Neovim for code browsing (don't write much code anymore but the code editor is still useful for reading code)”
“That’s a serious misreading of the NeoVim ecosystem, and I’d bet good money against your predictions coming true.”
“No such thing exist in neovim (or at least in times when I was using it), so that churn never ends.”
“I have found a huge productivity boost being able to stay in Neovim for extended periods of time”
“I moved to neovim (stable) with as few extensions as possible, and those I've pinned to some geriatric version.”
“nvim integration (for seamless split navigation and so that I can create or reattach to a tmux session in an nvim float”
“There have also been multiple breaking changes over the last five years, including breaking compatibility with established default vim keybindings.”
“I feel like the habit I’ve benefited the most from on my neovim journey has been reaching for :h before doing any web search.”
“the main advantages over Vim are just the Lua scripting instead of Vimscript, its support for language servers”
“at first I hated Neovim's poor AI ghost text. Now I kind of like the break from heavy AI when I write code”
“With its own package manager now, and LSP library, you really don't need a lot of config tweaking”
“neovim on android/termux is actually easier to use than any of the IDE editor apps mainly due to everything being keyboard based”
“I mainly use (neo)vim because it has a less distracting interface than any other full blown IDE.”
“neovim also parses the page and creates a table of contents, which can be used for navigation within the page”
“the vim state machine is always present underneath it, resulting in unwanted behaviors or impossibility to implement some things”
“I feel this is the superior paradigm: You don't even need to get to some specific location in order to edit it.”
“It's flat (technically modal, but that does not make it more casual) interface with everything as invisible hotkeys and a near command line interface”
“moved to Neovim for other reasons, chiefly performance/LSP nativity/plugin ecosystem vitality”
“youre using the keyboard to do most things anyway, so the keyboard can just stay open all of the time”
“Shellfish on iOS to ssh into a vps with tmux with Gemini-cli, lazygit and neovim worked quite well for me.”
“things like NeoVim break regularly as a result of friction between the immutable world and a lot of plugins”
“There is more flexibility to extend easily, to customise, to make my environment fit using these more”
“removing that micro-latency of "eye-to-mouse-to-tree" keeps you in the flow state much longer.”
“navigating and selecting things SYNTACTICALLY with nvim-treesitter-textobjects is life-changing”
“instead of switching back from the alt screen and giving you your terminal back, they open a gimped little window within vim which makes it hard to navigate, copy, and search for things in the output”
“a plugin you write for neovim can run in the terminal, in any Neovim GUI or in another application”
“The feature neovim gives to it's users, it the intuition and the confidence to reason about the code they've written.”
Counts come from 1,795,640 Hacker News comments, November 2025 to November 2026. How we count. Report a mistake.