<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>yoyohello13</author><text>Definitely agree about the enjoyable part. I don’t necessarily think vim has made me more efficient than normal keyboard+mouse, but I definitely find text editing a lot more enjoyable. It makes a really big difference in my state of mind during the day.</text><parent_chain><item><author>ChicagoBoy11</author><text>I have to be honest, seeing some content on YouTube and noticing some folks presumably putting things on the screen in the same speed as they were thinking is what got me into it.&lt;p&gt;I&amp;#x27;ve had a TREMENDOUSLY DIFFICULT time getting fully up and running with it in terms of workflow, but the text navigation alone has absolutely made me code not necessarily faster, but in a MUCH more enjoyable way. After a while it became difficult to imagine navigating a piece of code without some of VIM&amp;#x27;s core ideas, even if in my case it is down to mostly the feature-set related to easily navigating a file.&lt;p&gt;Alas, for me then the VScode-Vim extension is doing the trick, but since you mentioned the learning wall, curious if you know any resources or can suggest a path to move past it  nowadays.</text></item><item><author>eh9</author><text>I know it’s silly, but Vim is single-handedly responsible for people thinking I “code fast” in interviews. I always chuckle when someone notes how fast I can manipulate code and I think about the learning-wall I hit when first picking up Vim.</text></item></parent_chain></comment><story><title>Happy birthday Vim (2020)</title><url>https://groups.google.com/g/vim_announce/c/bQtQSHTK1sg</url></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>dharmab</author><text>For me it was a combination of:&lt;p&gt;- Reading through vimtutor&lt;p&gt;- Disabling my arrow key bindings and unplugging my mouse for a week (as part of a combined vim&amp;#x2F;i3&amp;#x2F;vimiuim learning experience&amp;#x2F;experiment)&lt;p&gt;- Playing Vim Adventures, a puzzle game based on Vim&amp;#x27;s controls&lt;p&gt;The three days of godawful productivity has paid off a thousandfold- especially when I later became temporarily disabled (broken bones in both arms) and couldn&amp;#x27;t use a mouse for a while.</text><parent_chain><item><author>ChicagoBoy11</author><text>I have to be honest, seeing some content on YouTube and noticing some folks presumably putting things on the screen in the same speed as they were thinking is what got me into it.&lt;p&gt;I&amp;#x27;ve had a TREMENDOUSLY DIFFICULT time getting fully up and running with it in terms of workflow, but the text navigation alone has absolutely made me code not necessarily faster, but in a MUCH more enjoyable way. After a while it became difficult to imagine navigating a piece of code without some of VIM&amp;#x27;s core ideas, even if in my case it is down to mostly the feature-set related to easily navigating a file.&lt;p&gt;Alas, for me then the VScode-Vim extension is doing the trick, but since you mentioned the learning wall, curious if you know any resources or can suggest a path to move past it  nowadays.</text></item><item><author>eh9</author><text>I know it’s silly, but Vim is single-handedly responsible for people thinking I “code fast” in interviews. I always chuckle when someone notes how fast I can manipulate code and I think about the learning-wall I hit when first picking up Vim.</text></item></parent_chain></comment><story><title>Happy birthday Vim (2020)</title><url>https://groups.google.com/g/vim_announce/c/bQtQSHTK1sg</url></story>