<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>tombert</author><text>I don&amp;#x27;t disagree with your thesis, but I should point out that I have been using Vim almost exclusively for almost six years now (well, NeoVim for 4 of those years), and my config is only about 40 lines, and most of it is just installing plugins for whatever languages I&amp;#x27;m using.&lt;p&gt;Despite me not hacking it like crazy, I still think it really shines as an editor; Vim macros were sort of life-changing to me once they clicked for me.  I also just think that modal editing is superior once you get past the initial learning curve.</text><parent_chain><item><author>ogre_codes</author><text>&amp;gt; My vim config is 600 lines. I have fixes for small annoyances. I have a bookmarking system set up in 45 lines. I have extra syntax highlighting for code snippets that are important to me because I’m doing things the original syntax maintainers never even considered. I create impromptu keyboard mappings and abbreviations and autocommands as needed for given tasks. I can move around in the design space at will.&lt;p&gt;I use VIM on and off, but I wanted to post the above because I think it exemplifies who might like using VIM.&lt;p&gt;VIM is ideal for people who find it worthwhile to spend the time building their configuration out. VIM is the productivity tool that gets better as you put the time and effort into building it out. If you aren&amp;#x27;t the kind of person who wants to put that time and effort in, it is still decent as a basic editor, but it doesn&amp;#x27;t really shine.</text></item></parent_chain></comment><story><title>I Still Use Vim</title><url>https://buttondown.email/hillelwayne/archive/why-i-still-use-vim/</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>threatofrain</author><text>My problem is that some of that building should&amp;#x27;ve been sensible defaults, and the community tends to outsource those responsibilities to extensions.&lt;p&gt;Which means your Vim experience now has some risk of rot. Once and awhile my configurations&amp;#x2F;extensions rot and I have to go and update myself as to what happened in the ecosystem, or what is interacting with what. One day I decided I&amp;#x27;m too tired and switched to VSC.&lt;p&gt;Also the author failed to talk about the #1 killer feature of VSC, the reason for its meteoric rise in popularity — intellisense.</text><parent_chain><item><author>ogre_codes</author><text>&amp;gt; My vim config is 600 lines. I have fixes for small annoyances. I have a bookmarking system set up in 45 lines. I have extra syntax highlighting for code snippets that are important to me because I’m doing things the original syntax maintainers never even considered. I create impromptu keyboard mappings and abbreviations and autocommands as needed for given tasks. I can move around in the design space at will.&lt;p&gt;I use VIM on and off, but I wanted to post the above because I think it exemplifies who might like using VIM.&lt;p&gt;VIM is ideal for people who find it worthwhile to spend the time building their configuration out. VIM is the productivity tool that gets better as you put the time and effort into building it out. If you aren&amp;#x27;t the kind of person who wants to put that time and effort in, it is still decent as a basic editor, but it doesn&amp;#x27;t really shine.</text></item></parent_chain></comment><story><title>I Still Use Vim</title><url>https://buttondown.email/hillelwayne/archive/why-i-still-use-vim/</url></story>