Yeah, it's definitely a matter of preference. For me, VS Code fails to be productive in a myriad of other ways which I cannot enumerate now because I always fo

Yeah, it's definitely a matter of preference. For me, VS Code fails to be productive in a myriad of other ways which I cannot enumerate now because I always forget them, and vim is the productive powerhouse I know inside out, where everything makes sense. So due to this I had the will to investigate and make this work the first time, which was painful back in the day, but now it feels rather out-of-the-box and automatic, especially since nvim 0.5.0 was released. I still sometimes fire up VS Code when I get frustrated with something, but I always find something else broken there and go back to nvim. One thing I'm eyeing though is Onivim 2, though it's not ready yet.