• I_like_cats@lemmy.one
    link
    fedilink
    arrow-up
    69
    arrow-down
    5
    ·
    1 year ago

    But that’s something new to learn and configure. I just want to code why should I spend my time learning another text editor when vscodium is fine

    • Potatos_are_not_friends@lemmy.world
      link
      fedilink
      arrow-up
      59
      arrow-down
      2
      ·
      1 year ago

      Careful. You’re in a linux-heavy audience. They’re the kinda people who would spend a few weeks setting up systems to use it for a few minutes.

        • No1@aussie.zone
          link
          fedilink
          arrow-up
          9
          ·
          edit-2
          1 year ago

          Well, it’s because after using the system for only a few minutes, I realise it’s not quite right, and I’ll have to spend a few weeks to set it up again!

      • U de Recife@literature.cafe
        link
        fedilink
        arrow-up
        8
        arrow-down
        1
        ·
        edit-2
        1 year ago

        That’s simply outrageous!!! As soon as I finish tinkering with my system, I’ll prepare a proper reply…

        On a more serious note though. Don’t overlook the role of procrastination in the endless tinkering many put on their boxes. I’m speaking from experience.

      • Synthead@lemmy.world
        link
        fedilink
        arrow-up
        6
        arrow-down
        1
        ·
        1 year ago

        I’m a full-time Vim and Linux user when writing code. I agree with the statement that “simply switching” editors is very naive. I’m my personal opinion, you should decide on an editor that makes sense to you and learn to be very good at it. If VS Code is that answer, then great. Not everything points to Vim or Emacs.

    • nonearther@lemmy.ml
      link
      fedilink
      English
      arrow-up
      17
      ·
      1 year ago

      Who doesn’t want to go through learning of text editor and pain of configuring instead of actually coding?

    • shotgun_crab@lemmy.world
      link
      fedilink
      English
      arrow-up
      6
      ·
      1 year ago

      That’s fine too. Use whatever does the job for you, but give alternatives a try if you ever have the time.

    • exu@feditown.com
      link
      fedilink
      English
      arrow-up
      4
      ·
      1 year ago

      Well, if you learned emacs, you could do everything in it and won’t have to change ever again! /s kinda

    • sugar_in_your_tea@sh.itjust.works
      link
      fedilink
      arrow-up
      3
      arrow-down
      3
      ·
      edit-2
      1 year ago

      Same reason why a carpenter should learn to properly use hand tools, or a teacher should keep up on literature. In other words, master your tools. It doesn’t matter which tool you use, provided you can use it to its full potential.

      I occasionally use VSCode, but I mostly use ViM because that’s my tool of choice.

      For another reason, if your ever in the situation where you need to work on something on a remote server or an unfamiliar machine, knowing ViM means you can at least be somewhat productive when you don’t have your normal tools available.

      • I_like_cats@lemmy.one
        link
        fedilink
        arrow-up
        1
        ·
        1 year ago

        I know vim. I’m using vscodium with a vim plugin. I was coding in pure vim for half a year because my Laptop with 4 gigs of RAM couldn’t handle vscode. I just don’t want to configure vim so it does all the stuff VScodium does for me

        • sugar_in_your_tea@sh.itjust.works
          link
          fedilink
          arrow-up
          1
          ·
          1 year ago

          That’s fine, use what works best. I think there’s value in getting at least the basics working, such as syntax highlighting and linting in case you want or need to use it again.

          The question was why one should learn to use something like ViM or emacs, not why anything else is a poor option. Master your tools, regardless of what they are.