Thread

1. sdcfgy · 1790523505 · focus · HN ↗

   I've used vim since the first time it appeared in Debian repos. I have been told a thousand times that NeoVim is better, more modern and solves many (conveniently never cited) issues. I just ignored it and carried on. Feeling terribly vindicated at this point as it's a feature I use regularly and have no idea that it would be an issue in NeoVim.

   1. WesolyKubeczek · 1790523829 · focus · HN ↗

      I used neovim because it felt way faster by default. I think treesitter runs circles around what classic vim is using to highlight syntax. That said, I never used both beyond basics, thus no horror stories either.

      1. sdcfgy · 1790524012 · focus · HN ↗

         I haven't noticed any performance issues in vim to start with. It was fast on a 75MHz pentium for me. The syntax highlighting, same. No issues. I don't always use that though because I can't be bothered to set up anything much past the basic config.

         1. flohofwoe · 1790526234 · focus · HN ↗

            IIRC vim became really slow with the combination of large source files (thousands of lines of code) and language server plugins (e.g. code completion and live error squiggles).

            1. sdcfgy · 1790527336 · focus · HN ↗

               I had a C program that was a single file 140,000 lines long back then. No issues.

               1. kelnos · 1790548771 · focus · HN ↗

                  Ah yes, the "I've never had this problem so obviously no one else could have possibly had it" argument.

                  1. sdcfgy · 1790581351 · focus · HN ↗

                     No it's more the "what the hell are people doing to make their lives difficult?" argument.
                  2. rmwaite · 1790601440 · focus · HN ↗

                     To be fair, they were just sharing their experience. I don’t recall them saying anything close to your interpretation.

Unofficial Hacker News client; not affiliated with Y Combinator.