For me, I really want to get into niri, but the lack of XWayland support scares me (I know there’s solutions, but I don’t understand them yet).
Also, I stopped using Emacs (even though I love its design and philosophy with my whole heart) because it’s very slow, even as a daemon.
Neovim. I tried to use it a year ago, but I felt like I was fighting it every time I just wanted to make progress on my project. VSCode doesn’t get in my way. I’m going to give it another shot in a few years.
If you aren’t already, you could get familiar with the vim motions within VSCode via a plugin. Moving over to a vim setup can be overwhelming, setting up your lsp,linters, other packages. Adding on the need to still learn key bindings makes it extra difficult. I started with VSCode using vim motions, went to doom emacs and used evil mode and then my mentor got me hooked on vim. Do it in steps and you’ll get to a config that lets you code without much fussing, good luck!
Try kickstart.nvim. I was skeptical until I tried it. It’s a very good starting point for Neovim. Pretty much eberything else I’ve ever tried is either too bloated, too complicated, too outdated, too overwhelming, or a mix of the above. Link: https://github.com/nvim-lua/kickstart.nvim
Haven’t used neovim, but I had to try vim way too many times. I can’t use anything else now.
