• frezik@midwest.social
    link
    fedilink
    arrow-up
    5
    arrow-down
    2
    ·
    9 months ago

    Sure, you can code in Vi without plugins, but why? Leave your elitism at home. We have deadlines and money to make.

    Nothing elitist about it. Vim is not a modular tool that I can swap out of my mental model. Before someone says it, I’ve tried VS Code’s vim plugin, and it sucks ass.

      • frezik@midwest.social
        link
        fedilink
        arrow-up
        1
        ·
        9 months ago

        Certain shortcut keys in vim conflict with shortcut keys in the IDE. The flow doesn’t work the same.

        • KeenFlame@feddit.nu
          link
          fedilink
          arrow-up
          1
          arrow-down
          1
          ·
          9 months ago

          I don’t understand how you think you will convince anyone that you can’t use vim, when so many do that without problems

          • frezik@midwest.social
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            9 months ago

            Please avoid double negatives. I’m not quite sure of the meaning of your sentence.

            If you’re saying I have issues using vim if I can’t use it in an IDE, no, that’s not how it works. If you use simple vim (not much more than knowing how to get in and out of edit/visual mode, and use hjkl for navigation), then it’s fine. Once you get into more advanced vim features, though, the key presses in vim get picked up by the IDE first, so IDE shortcuts take precedence.

            If someone were to learn vim inside an IDE and develops it organically as part of their flow, it’d be fine. If you already have a lot of standalone vim flow setup in your mind, it’s a problem.