I tried Vim for the first time many years ago. I did not get very far. In fact I was just stuck trying to figure out what was going on. I naïvely thought I would be cruising within 10 minutes. I mean, how hard is it to learn a few key bindings, am I right?
Wrong. The Vim editor is different world altogether. Modal editing and key bindings will have you running away with your tail tucked neatly between your legs. I was pleased to open up my Sublime Text 2 editor with my Space Grey theme and felt safe again!
Since that experience I have encountered Vim more times than I realized. Every time I would commit after a merge in my command line, I was using Vim. I didnt give it much thought and just accepted that this was part of merging.
Nowadays I use lazygit, so I dont see Vim much anymore. My curiosity for Vim however, has crept back after watching Primeagen wiz around in his Vim editor. I think I am ready to give it another shot. I mean, being able to remove more hurdles while programming, what's not like?
So far, I have started my journey with Vim by playing around in Vim Tutor. I am also following the guidelines set up in this article. So far, I'm liking what I see. I am far from adopting it into my professional workflow, but maybe in a year or two, this might happen. Expect to see more posts on my experience as a frontend developer jumping into Vim.
-Trolz
Wrong. The Vim editor is different world altogether. Modal editing and key bindings will have you running away with your tail tucked neatly between your legs. I was pleased to open up my Sublime Text 2 editor with my Space Grey theme and felt safe again!
Since that experience I have encountered Vim more times than I realized. Every time I would commit after a merge in my command line, I was using Vim. I didnt give it much thought and just accepted that this was part of merging.
Nowadays I use lazygit, so I dont see Vim much anymore. My curiosity for Vim however, has crept back after watching Primeagen wiz around in his Vim editor. I think I am ready to give it another shot. I mean, being able to remove more hurdles while programming, what's not like?
So far, I have started my journey with Vim by playing around in Vim Tutor. I am also following the guidelines set up in this article. So far, I'm liking what I see. I am far from adopting it into my professional workflow, but maybe in a year or two, this might happen. Expect to see more posts on my experience as a frontend developer jumping into Vim.
-Trolz