Swap Vim for something else only if you want different defaults, not just different keys. Modal editors with modern features suit people who like the modal model, small terminal editors suit anyone who wants almost no learning curve, and the remaining options suit people who want either a whole working environment or a minimal modern editor. Decide which you are first.
Vim describes itself as a highly configurable text editor built for efficient text editing, and it's an improved version of the older vi editor. People go looking for something else for different reasons: a wish for modern code features out of the box, a teammate who needs something gentler, or simple curiosity about how other editors approach the same job.
Here are seven editors, first sorted into three styles, then covered one at a time from A to Z.
Three styles of editor to choose from
- Modal editors: Helix, Kakoune and Neovim keep separate modes for moving around and for typing.
- Small terminal editors: GNU nano and micro, the second of which calls itself modern and intuitive.
- Two different directions: GNU Emacs reaches well past text, and Zed bills itself as minimal and built for speed.
If you love modal editing but want something fresher, stay in the first group. If you want something that works without modes, the second group is the place to start. If you want your editor to become a whole working environment, or the opposite, a minimal modern one, look at the third.
Plugins don't travel between these editors
This is the trap for anyone with years of customisation behind them. Helix's own FAQ says it has no plugin system yet. Neovim's vision page lists Vim9script support as a non-goal. So modal editors that look alike aren't drop-in replacements for each other's plugin collections.
Before you move, list the plugins you'd miss most. For each one, check whether your new editor has it built in, offers an equivalent, or has nothing. That ten-minute exercise tells you more than any feature comparison, and it stops the classic mistake of switching on a Friday and spending the weekend rebuilding what you had.
A short family tree
The modal editors here are related, and knowing how helps you guess what will feel familiar. The vi editor came first; its improved version is the one you're leaving, and its own site notes that vi is distributed with most UNIX systems. Neovim is built on that improved version in turn, and says it's for users who want the good parts and more.
Helix sits on a different branch. Its own page says its multiple cursors, a core editing primitive, were inspired by Kakoune, where multiple selections are the central way of interacting with text. So if select-first editing appeals, try Kakoune and Helix together and see which one your fingers prefer.
The seven editors, A to Z
GNU Emacs
Far more than a text editor, which is the appeal for people who want one environment for many jobs and don't mind investing time to shape it. If it's the one tempting you, our look at the two old rivals covers that choice in depth.
GNU nano
A text editor from the GNU project, with its own homepage. Open its built-in help on day one and judge it on a real file before you decide.
Helix
Built in Rust, for the terminal, with multiple cursors as a basic building block. For now, what ships is what you get, so there's no plugin list to tend.
Kakoune
A modal editor centred on multiple selections, for people who like to select first and then act on everything they've chosen.
micro
It calls itself a modern and intuitive terminal-based text editor, and you can extend it with plugins written in Lua, installed through its own plugin manager.
Neovim
A Vim-based editor built for extensibility; its own description calls it hyperextensible.
Want AI doing the heavy lifting in your marketing?
I build the systems that handle the boring 80 percent, so you get your week back. Done properly, with the human kept in.
Zed
It describes itself as a minimal code editor built for speed and collaboration with humans and AI. If you want a modern editor rather than a terminal tool, it's the one here built around working with other people.
How they line up
| Editor | Style | Stand-out claim |
|---|---|---|
| GNU Emacs | All-in-one | Much more than text editing |
| GNU nano | Small terminal | A GNU project editor |
| Helix | Modal | Multiple selections, no plugins yet |
| Kakoune | Modal | Multiple selections at the centre |
| micro | Small terminal | Lua plugins with a manager |
| Neovim | Modal | Hyperextensible |
| Zed | Minimal code editor | Speed and collaboration with AI |
Use the table to pick two candidates from one style, then run them side by side with the switch plan below. Comparing a modal editor with a small terminal one tells you which style you want, not which editor.
What you'll miss, and what you won't
Long-time users tend to miss the same things after a switch: muscle memory for motions, a carefully tuned config, and plugins that quietly did a job for years. The motions come back quickest if you stay in the modal group. The config and the plugins rarely come back as they were, whichever editor you pick.
What you can leave behind is the maintenance. A fresh start is a chance to keep only what you use every week, and to write down why each setting exists so the next move is easier.
Choosing for a teammate, not yourself
Sometimes the search starts because a colleague keeps getting stuck in a modal editor on a shared server. In that case your own preferences don't matter much. What matters is that they can open a file, make a change, save and leave without asking for help.
Pick from the small terminal group, show them the handful of commands they'll need, and leave your own setup alone. You can keep editing the way you like while they get on with their day, and nobody has to learn modes they'll use twice a month.
A gentle way to switch
- Write down, in one plain sentence, exactly why you're thinking of leaving.
- List your five most-used plugins and check each against the new editor.
- Use the new editor for one real task a day for a week, keeping your old one for everything else.
- Learn the new editor's built-in tutorial or help before copying anyone's config.
- Copy across only the settings you miss after a week, not your whole old config.
- Decide after two weeks. If you keep reaching for the old editor, that's useful information too, and going back is a perfectly sensible result.
Frequently asked questions
What should a complete beginner try first?
Something without modes. The less there is to remember on day one, the more likely they are to stick with it.
Will my vi keys carry over to Helix or Kakoune?
Only partly. They're modal editors on a different branch from vi, built around multiple selections, so expect to relearn some habits.
Why put multiple selections at the centre of editing?
It lets you mark many places at once, then change them together in one go.
Will a new editor slow me down at first?
Yes, for a week or two while new habits form.
Which of these runs on most UNIX systems by default?
Of the family named here, its own site says vi is the one distributed with most UNIX systems, so it's a safe fallback on an unfamiliar server.
