I've been using Vim for over 10 years. The first few years I used it badly. Later I took time to really learn it. Now I can use it fairly decently, but I still learn new things every now and then.

It feels like a really good investment. It's been around forever, it's gonna be around forever, it's installed on almost all computers, and you're going to be forced to use it at some point or another.

I really enjoy being able to go to any computer and starting up a familiar editor, without installing or configuring stuff. I also use a very vanilla Vim. If a coworker's laptop or some server has a different Vim config than mine, I can usually do vim -u NONE to get back to a familiar place.

Helix because it's easy to setup and hassle free, and it runs well on my 2009 ASUS Eee

Neovim genuinely makes me happy. I love it to bits.

vscodium and neovim extension

vscodium. Easy to use for beginners (i'm a beginner too), fully open-source, all microsoft tracking binaries removed. Aviable for Windows, Linux, macOS, darwin, propably bsd, or even as a webview, and supports a lot of architectures. Great for intrepeted languages, but supports compiled ones too

Zed, Helix, and VSCodium for the Windows side.

I use VSCodium atm.

I use Lapce, which could be a great native alternative to VS-Code (Also it's built with Rust, this is for the Rustaceans)

There was a time where I used Geany as well, I still like it

I use emacs when on my personal machines. VS Code at work.

The fastest tool is the one you are best at using. I find that my tool doesn't make me fast, my ability to solve issues makes me fast. I very rarely learn a new tool unless it accomplishes something for me my other tools do not.

For example, at work I use windows and regularly ssh to servers. My entire job is spent ssh'd into other servers. Emacs terminal emulator is spotty at best when using ssh on windows. There are ways to make it work, but some modifications get flagged by our SEIMs. So in that case I use vs code, and the ssh remote connection options and split terminal interface.

At home I use emacs. I have all Linux machines so my terminal plays nicely. I also am working on reducing my RSI from years of tech work. The less mousing I have to do, the better. Emacs allows me to keep my hands on my keyboard.

I hate to be that guy but (neo)vim has served me well for too long. I don't even use any crazy maps or plugins; it's just comfy.

I swapped to neovim 10 months ago. Haven't looked back. Actually, I've looked back a LOT for the first few weeks because I couldn't figure out how to do certain things. But the more you learn the better it becomes. Not needing your mouse is SO good.

I used to use VSCodium, but in my quest to touch the mouse as little as possible I switched to Neovim.

I'm still learning to code, but I tried out a bunch and I've liked using Vim, VScodium and Pycharm.

NeoVim plus tmux.

Great multi dimensional way of operating. You have access to the terminal and your ide.

It's beautiful

The main reason I like vi/vim is that if you're having to use multiple different computers (such as if one is a sysadmin, or in my case, does scientific computing), because if you're running on Linux, you can be confident that vi/vim will be on it.

For personal use, I've been using emacs, but I can't recommend that without feeling like I'm suggesting you try some heroin. I enjoy emacs because of it's complexity and how much power it gives me to modify it. It's very easy to fall into feature creep and over complexity though. That's why I can't recommend it — it's good for me because I am a chronic tinkerer, and having something to fuck around with is an outlet for that.

I would recommend learning the basics of vim though. As you highlight, getting back to your current level of productivity would take a while, even if you loved vim and committed to it wholeheartedly. It is possible to try it out with little commitment though, for the perspective. If you're on a machine that has vim installed already, try the vimtutor command, which will start the ~30 min long inbuilt tutorial for vim. I liked it for giving me perspective on what on earth vim even was.

I know you don't use it anymore, but I just want to fistbump you re: sublime text. I really loved that as a basic text editor that was, for me, just a slightly nicer notepad.

I use Neovim. It feels like a second nature after using it for years. I love how effortless the interaction with the editor is after you have spent hundreds of hours learning it. I have no reasonable arguments to convince anyone to do that though. I just do it because I enjoy the hell out of it 🤷‍♂️

vscode + whatever connection plugin you need + vim plugin

Do you have a minute to talk about my lord and savior VIM? Wanna see my dot files?

My editors

• Professionally I use Jetbrains stuff (intellij, pycharm, etc).
• At home I use Neovim because I like to have lsp support, I'm too cheap to pay for IDE's and I dislike VSCode for personal reasons. For quick edits I use default text editor e.g. kate/gedit.

My opinions on learning new editors

• If you need to go fast now, use what you know best.
• If you have time to learn just try whatever looks cool. Learning a new editor/way to edit text will broaden your horizons even if you don't end up using it.

Not dev but I'm in IT/Cybersec mostly as it's much easier to find jobs there and I use vim just about everywhere, usually with tmux and i3 with custom vim-like keybinds (super+j move focus right etc), I use vim even on my phone in termux, with gboard.

I don't use LSPs cause CBA but I only use Python and C and maybe occasionally bash for homelab stuff and I don't have large projects (😭).

If I'm doing any ML stuff from scratch (not refining or writing API for local llm model or integrating it with another API but just building classifiers etc) for fun I use Jupyter. Such a wildly different way of coding honestly ngl it's wild, but great when you need to document what you're doing.

At uni I used to use fucking Visual Studio with C# and Netbeans with Java, but I learned it pretty well. I don't think they ever even taught us how to run code outside those 😂

At work I use gedit and gnome terminal for navigation cuz it's company time unless I'm personally interested in what I'm doing.

Fresh from university I found a job with terrible keyboards. After about 4 months I started to feel constant pain in my wrists. I then switched to vim.

And it solved my wrists issue. But also, I discovered a way to edit text that was so much optimized fat beyond my expectations.

I wrote this article for people that would like to familiarize with vi keybindings.

https://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/

I keep hearing about how modal editing is faster

Please, do yourself a favor and ignore that noise. It is more a question of like/dislike and training. Personal sidenote: I daily alternate between PhpStorm and Neovim. Can't say doing things in either is faster/slower to any significant degree (PhpStorm is mostly there for the things I have not yet configered properly in Neovim, like looking through git history)

and I would like to switch to a more performant editor

This should be looked at and tested objectively: is it working with big files that is the problem? Or navigating the code base? Or something else? Maybe it is better to tweak vscode instead?

+1 for Helix. Selection then action always made more sense to me than action then selection.

I use the godot integrated code editor, but i am debating switching to writing the code in google slides and copying the text into notepad in a virtual machine

Mostly emacs, vi, or what IDE I happen to be using like Eclipse.

Amateurs. I use butterflies.

https://xkcd.com/378/

Doom Emacs

I just use Vim out of habit. I've been using it as my main text editor since I was like 13 or so, maybe more like 10 I don't really remember. It works perfectly well for the vast majority of my use cases. I use Jetbrains IDEs if I feel I need the power of a full IDE. Jetbrains has an IdeaVim plugin if you want it to be a modal editor, or if your fingers are accustomed to Vim keybindings.

I use Emacs and love it. It's an amazingly frustrating (and just plain amazing) piece of software, but it's hard to move away from it because it's the only thing like it. Maybe if Lem every gets mature enough I might switch.

I probably wouldn't recommend it though as it doesn't sound like what you're looking for.

On windows i use vscodium, on linux neovim.

As others say i think helix is cool, but the limited customization is kind of meh for me. I love the keybinds for it though.

I use pycharm at work for most things. Work paid for it. It has some nice stuff i like. I'm sure other editors do all of this, too, but nothing's been causing me enough pain to switch

• Database integration. Little side panel shows me the tables, and I can do queries, view table structure, etc, right here
• Find usages/declaration is pretty good. Goes into library code, too.
• The autocomplete is pretty good. I think they have newfangled AI options now, but the traditional introspection autocomplete has been doing it for me.
• Can use the python interpreter inside the docker container
• The refactor functions are pretty good. Rename, move, etc
• Naive search is pretty good. Can limit it to folders, do regex, filter by file name, etc

It does have multiple cursors but I've rarely needed that.

I use sublime for quick note taking. Mostly I like that it has syntax highlighting, and it doesn't require me to explicitly save a tab for it to stay open

VSCode with the Vim plugin most of the time. Vim if I'm just editing something small and was already in a terminal.

Every IDE worth trying has Vim mode or a plugin for it, you don't need to use actual Vim to benefit from it!

VS Code with your favorite plugins is pretty fantastic for any editing in my experience. I've tried others and they do seem to work well, but not well enough to warrant switching, and they often come with quirks that are just annoying enough to make me want to switch back.

I suggest trying others to know what's out there, even if you ultimately end up back on VS Code.

I've used everything, vim, nvim, emacs, visual studio, vscode, sublime, codeblocks, android studio, xcode, bloodshed, intellij, eclipse, VB, geany, dreamweaver, qt, atom, and cursor (even though it’s really just a plugin)

It doesn't matter. It will never matter. I use vscode today because it handles everything I throw at it and it's easy to make extensions for. Or cursor if I'm feeling lazy, the agentic mode with claude is pretty damn good if your codebase is well established.

Don't get hung up on the editor, just use the tools available to get the job done, at the end of the day programming is converting concepts to text.

I use vim, or spacemacs with evil mode (emacs distribution with sensible shortcuts and vim emulation). Or VSCode with spacemacs emulation.

You will pass your current productivity in less than a month. All of the things you describe are easily done in VSCode with vim emulation (I prefer the full spacemacs emulation but it's not actually a huge difference). You won't have to move your hands away from the normal typing spot on your keyboard -- no home and end, just 0 and $. No control+arrow keys, just w and b (or e or even more motion options). Highlighting is as easy as v and then motion commands. And there are so many more useful things that vim (and vim emulation) make simple and fast. Orthogonal VSCode features like multi cursors still work.

I've moved on from vim to neovim, and I think I'll continue using something in that family in the future. It's a pretty stable experience overall, but the inclusion of LSPs and tree-sitter have been good improvements too.

Ultimately editors are tools, similar to keyboards, os-es, screens, chairs, shoes and so on. There are some objective quality differences between a well-constructed tool and some slapdash nonsense, and there are a huge amount of subjective quality differences. What suits me may not suit you, and vice versa.

It's generally good to try out some new (to you) stuff and see if you like it. If you do, great; if you don't, well, now you know. I think my worst experience was with Acme (or Wily? can't remember), during a phase where I experimented with Plan 9 stuff. Ultimately very not my cup of tea, but apparently Rob Pike (who made it) and some other gophers still enjoy it? Which is good for them, just like it's good for me that I can choose not to use it. It's just personal tastes, and I still think it's good that I gave it a go.

The debate over holding down modifier keys vs modes is also a part of the Emacs vs vi debate from many decades ago. There might be some statistics for what works best for the most people now, but again, use what suits you. And try some new stuff when you get curious, it's generally good for you.

Sublime text, vi, eclipse, emacs depending what I'm doing

Dev of 25 years here: Cursor, for the LLM integration. It's based on VSCode, just way tighter AI integration. It's so good.

Zed, for the last few months, and happy with it (previously vscode) - I code in Scala, so Metals provides the complex hints / actions.

xfce text editor and sublime text, and vim but only when i want to work within the terminal

Most code I write is Java and I use IntelliJ for that. When I write Python I use PyCharm, anything else, Visual Studio Code or VSCodium.

All of these have plugins for vim keybindings which are always the first thing I install. I almost never disable them.

@verstra I use Jetbrains for pretty much anything except C++, their editors are the best. I use it for PHP, Go, Java/Kotlin, C#, databases, Typescript and I'm probably missing something.