First time when you ssh into your Linux terminal and you gotta “sudo crontab -e” or something and it’s like “what editor do you want to use?” and nano sounds lame so you choose vim cause the sound is cool when you say it and then you have to wipe the whole comp and start over

  • Voroxpete@sh.itjust.works
    12·
    11 个月前

    I am a professional linux sysadmin, and I don’t use Vim. There is honestly no task you will ever do that will actually require familiarity with Vim. You can get by with Nano just fine.

    • Fitzsimmons@lemmy.blahaj.zone
      3·
      11 个月前

      I use nano on my servers because the default configuration can be used by pretty much anyone, even if I had to explain it to someone over the phone. And hopefully you rarely if ever have to make sophisticated changes to files on servers that would benefit from vim’s model.

      If you do need to do consistent heavy-duty file editing on a server, rmate is really nice for that: https://github.com/aurora/rmate

      But honestly both of these strategies are dated and I don’t use either of them professionally. These days it’s all immutable infrastructure: I use my local editor to make build scripts for immutable server images that there’s no point in editing files on running instances because none of the changes will be persisted.

      • Voroxpete@sh.itjust.works
        2·
        11 个月前

        Exactly. The days of doing long form editing directly on your server are gone. Most likely any editing I’m doing is happening in VSCode or Notepad++/qq.