Same vim simulation plugins (albeit far less powerful) exist in most common IDEs.
I still go back to it for major refactors and gnarly merges, because the LSPs from jetbrains are unparalleled. But as a result of their features it is incredibly laggy and slow compared to neovim, not to mention so RAM-heavy.
After adjusting to such high quality and fast nvim plugins like telescope, it makes the jetbrains editor feel like I’m moving through molasses to do a project-wide search, for example. And the vim simulation doesn’t (can’t?) support some of the more advanced features, or some really great plugins.
The biggest difference is in individual key latency though, I notice regular stutters while typing in the jetbrains IDEs that just don’t exist in nvim. It just throws me off if I’m in the flow typing and the input just freezes for a couple hundred ms..
I’m currently testing Helix [1], which is a terminal editor with Vim-like keybindings — but which requires no configuration or plugins (LSP works out of the box, sensible leader keybindings by default, multiple cursors is built in). It lacks some features like snippets and folding though. Vim -> Helix reminds me of when I switched Zsh -> Fish: I lost some power, but it did 80% of what I wanted from a custom config without any work. Remains to see whether I’ll stick with it long-term though.
In the past few years, the plugins fzf.vim and telescope.nvim made vim/nvim my go-to by making vim/nvim ridiculously more useful. Taking the time to set these up to your liking really pays off. Eventually, I moved completely to nvim.
I love the nvim project especially for how it rejuvenated the vim landscape and the cutting edge plugin ecosystem.
For rust development, rust-tools.nvim and rust-analyzer has fared really well compared to VSCodium.
I used vim as my main editor in the past 10 years and went through vimcasts near the beginning of my professional career. In January this year I switched to an IDE and I'm surprisingly ok with that. I did that because I moved to a different programming language and wanted better discoverability as well as an environment that "just works".