• KiranWells@pawb.social
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 year ago

    When I first tried Helix, my main concern (that prevented me from getting too far into it) was not going from Vim to Helix, but the other way around. Vim (or sometimes vi) is a standard editor on almost any Linux machine, so if I am ever working on a server if a VM, I would need to know/use Vim keybinds. That made Vim a more useful tool for me to learn at the time, as I could use the skills both on my machine and anywhere else.

    • nachtigall@feddit.de
      link
      fedilink
      English
      arrow-up
      7
      arrow-down
      2
      ·
      1 year ago

      I don’t feel like this is true anymore. Many distros do not ship vi(m) anymore but only nano.

    • Fryboyter@discuss.tchncs.deOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Vim (or sometimes vi) is a standard editor on almost any Linux machine, so if I am ever working on a server if a VM, I would need to know/use Vim keybinds.

      I understand the argument, but in my opinion it is used far too often and is not always true.

      Not everyone works with servers on which they have no influence on the installed software.

      And in the few cases where I had to work with servers on which I had no influence on the installed software and on which actually only vim was installed, I could always use sshfs or rclone mount without any problems so that the editor I used didn’t matter.