Nano has already supplanted the great EMacs and Vim as the most popular text editor of all linux distros, for though it has many omissions in functionality it scores over the older, more complete programs in two important respects. First, it is slightly simpler; and secondly it has the text “^ Exit” inscribed in highlighted text on its footer

EDIT : This sees to be going over some people’s heads. It’s a hitchiker’s guide to the galaxy reference.

The Hitchhiker’s Guide has already supplanted the great Encyclopaedia Galactica as the standard repository of all knowledge and wisdom, for though it has many omissions . . . it scores over the older, more pedestrian work in two important respects. First, it is slightly cheaper; and secondly it has the words DON’T PANIC inscribed in large friendly letters on its cover.

  • edinbruh@feddit.itEnglish
    34·
    15 hours ago

    It’s there and it’s easy. Most people don’t use terminal text editors unless they are SSHing in a server, and they would only do that sporadically, so it makes no sense to become proficient in a complex text editor like vim or Emacs for that little use case.

    Sidenote: personally, I learned vim once, and used it extensively every day for two years. I stopped using it for one year and was back to square one. Now I use vscode for everything… Even when I’m using SSH, because vscode supports SSH

    • Zarobi@aussie.zoneEnglish
      1·
      4 hours ago

      I only use terminal text editors anymore when I need to edit config files à la sudo nano. I just don’t trust visual text editors to do that stuff, I’ve been burned too many times in the past. Files “saving” but not actually saving. Files actually corrupting or changing ownership on save. Etc. Good old nano, doesn’t fuck with the critical system files any more than I already am.

    • jaybone@lemmy.zipEnglish
      72·
      14 hours ago

      It’s kind of sad that many people don’t use the shell / terminal anymore, especially as part of their regular development flow. There’s so much scripting and so many shell commands you can use that will do things you just can’t do in vscode. And having an editor like vi immediately available is part of that flow.

      For me, vim and the shell are my primary IDE. I rarely fire up vscode. But I guess I’m getting old. Still faster than the younger devs who mainly use vscode and then struggle when they are forced to use the command line due to whatever circumstance where vscode is not available or appropriate. Kind of makes me sad. Feels like a valuable skill is being lost.

      • fxdave@lemmy.ml
        1·
        3 hours ago

        I used vim, vim based stuffs, spacemacs, jetbrains, netbeans, atom etc… Now I use mainly claude code, sometimes, rarely I also open vscode. Shame because I know a lot of shortcuts, but not needed.

      • edinbruh@feddit.itEnglish
        8·
        13 hours ago

        Oh, I use the terminal a lot, it doesn’t throw me off. When I can’t have vscode (e.g. small openwrt devices) I can use vim. It’s just plain easier to use vscode for editing files when I can

    • scrion@lemmy.world
      51·
      14 hours ago

      Every editor “supports” SSH, you can mount files on a remote SSH server via SSHFS.

      • edinbruh@feddit.itEnglish
        9·
        12 hours ago

        And instead vscode supports SSH (without quotes), you can connect to an SSH host, and it will open files and folders on the host like it does locally. And if you open the integrated terminal it will run on the remote host. And it will forward the git login agent so you can commit or push with the credentials of your local machine. And it can forward ports from the remote.

        • scrion@lemmy.world
          2·
          4 hours ago

          Sure, but none of that is special in any way. That’s just what SSH does already. If you like that to happen in your editor GUI, by all means, you do you.

          What I’m saying is not a single of those features is an accomplishment of vscode and you can do that with every editor you like, or even without any. I didn’t want people to believe they’d need to switch to vscode to achieve any of that. That was my angle.

          I can’t and I’m not going to comment on the integration or the workflow, if you’re the audience for those kinda things, it’s probably great, give vscode a try. It’s probably obvious that I am not but hey, different strokes and all.