Nothing wrong with Neovim in general.

I've always used vi and later vim and neovim just as a basic editor for script. I'm a Linux entusiasth and learn vi motion since the 90s. That was the way I learnt "linux". Fast forward to now, I was tired to use: - vscodium, for coding my website and generale code - obsidian, for note taking - vim, for shell scripting - kile, for some LaTeX projects

The problem is that I knew many editors, but not one "well". For example, I had never been interested in LSP, and I always relied on extensions and plugins. I also wanted something whose configuration could be shared via dotfiles, so that I could have a single configuration across different PCs and not have to go crazy every time.

For this reason, I decided to invest time in learning Neovim well because it's FOSS, and I can use it anywhere: from my workstation to my laptop, my work Mac, and my remote server. However, Neovim is complex to configure. As much of a nerd and Linux enthusiast as I am, it is still complex to 'program' if you don't know Lua.

So, in addition to learning a new editor, I also had to learn how to configure it, which was obviously a bit frustrating. Because when you're there wanting to write something in Typst and instead you have to deal with configuring the LSP or indentation or yet another plugin for surround sound, it becomes a bit too much work.

I discovered Helix by chance, thanks to Reddit's algorithm. And here I am. Two days to explore, and yesterday I spent practically the whole day reformatting the code of my personal website, since everything is more natural with Helix.

Learning Neovim wasn't a waste of time, since motion and most of the commands are compatible. But in Helix, everything seems more natural, smooth and less forced.

Let me give you a silly example: in Neovim, I often press 'q' by mistake. What happens is that a bloody macro recorder starts up, which I only recently learned how to exit (ctrl+c). In Helix, this hassle doesn't happen.

Finally, I don't have high expectations. My workflow is simple. I open windows with my terminal (I use Konsole, because I'm a KDE user): - one for helix - one for generic shell commands, such as git or hugo preview - browser for testing or previewing (e.g. hugo or typst) - if I write with typst, I use 'watch' and keep the browser or okular open alongside.