git.stevedylan.dev

Merge branch 'main' of https://github.com/stevedylandev/stevedsimkins-dev-astro 5b7e44a5

Steve · 2024-08-26 10:38 1 file(s) · +1 −1

src/content/post/leaving-neovim-for-zed.mdx +1 −1


### Vim Mode

While in the middle of my time with Neovim I came across other frustrated Neovim users that found themselves spending too much time fixing issues in Neovim to the point they switched to VSCode. Of course I had a few moments like this myself and I wondered if I had missed something. At this point I had a much faster computer, so I figured I would give it another shot. Of course I downloaded the Vim plugin as the Vim keybindings are worth learning no matter what text editor you use, and it was incredibly disappointing. Nothing had every felt so buggy and jagged, and it remained one of the big reasons I couldn't stick with VSCode. I was back in Neovim within a week or two.
While in the middle of my time with Neovim I came across other frustrated Neovim users that found themselves spending too much time fixing issues in Neovim to the point they switched to VSCode. Of course I had a few moments like this myself and I wondered if I had missed something. At this point I had a much faster computer, so I figured I would give it another shot. Of course I downloaded the Vim plugin as the Vim keybindings are worth learning no matter what text editor you use, and it was incredibly disappointing. Nothing had ever felt so buggy and jagged, and it remained one of the big reasons I couldn't stick with VSCode. I was back in Neovim within a week or two.

When I was considering Zed again I read [a blog post](https://registerspill.thorstenball.com/p/from-vim-to-zed) about the custom Vim mode built into Zed. This was not a third party plugin; this was a labor of love from the developers building Zed. They've made it clear that they don't plan to port absolutely everything to Zed, but they have done a fantastic job supporting the important stuff that makes the editor an S-tier experience.


65	65
66	66		### Vim Mode
67	67
68		-	While in the middle of my time with Neovim I came across other frustrated Neovim users that found themselves spending too much time fixing issues in Neovim to the point they switched to VSCode. Of course I had a few moments like this myself and I wondered if I had missed something. At this point I had a much faster computer, so I figured I would give it another shot. Of course I downloaded the Vim plugin as the Vim keybindings are worth learning no matter what text editor you use, and it was incredibly disappointing. Nothing had every felt so buggy and jagged, and it remained one of the big reasons I couldn't stick with VSCode. I was back in Neovim within a week or two.
	68	+	While in the middle of my time with Neovim I came across other frustrated Neovim users that found themselves spending too much time fixing issues in Neovim to the point they switched to VSCode. Of course I had a few moments like this myself and I wondered if I had missed something. At this point I had a much faster computer, so I figured I would give it another shot. Of course I downloaded the Vim plugin as the Vim keybindings are worth learning no matter what text editor you use, and it was incredibly disappointing. Nothing had ever felt so buggy and jagged, and it remained one of the big reasons I couldn't stick with VSCode. I was back in Neovim within a week or two.
69	69
70	70		When I was considering Zed again I read [a blog post](https://registerspill.thorstenball.com/p/from-vim-to-zed) about the custom Vim mode built into Zed. This was not a third party plugin; this was a labor of love from the developers building Zed. They've made it clear that they don't plan to port absolutely everything to Zed, but they have done a fantastic job supporting the important stuff that makes the editor an S-tier experience.
71	71