• udon@lemmy.world
    16·
    6 months ago

    tbh, one of the essential things vim gets right for me is that it’s designed as a text editor, not (only) a code editor. I use it for so much non-code text as well, but it feels weird opening a coding tool for such things.

    • corsicanguppy@lemmy.caEnglish
      5·
      6 months ago

      It’s great to use an editor designed and built when vietnam and leaded gas were all the rage.

  • 🦄🦄🦄@feddit.org
    152·
    6 months ago

    Have been a professional software engineer for 8 years now. Have yet to find a reason to use vim for anything (other than availability of course, but if nano isn’t installed for some godforsaken reason I have other problems lol).

    • toynbee@lemmy.world
      201·
      6 months ago

      I’ve been in various forms of coding and administration for around fifteen years now. Despite trying lots of editors, I have yet to find a reason to use anything but vim.

      I do like obsidian for note taking.

      edit: Removed typo.

    • CubitOom@infosec.pubEnglish
      5·
      6 months ago

      I used to think this way. Until I found that with emacs you can edit any file on an SSH enabled computer remotely. Meaning that not only are you no longer constrained by what the computer has installed. But you can use your personality configured editor while editing that file. It’s called tramp.

      BTW, with Emacs you can use vim key bindings evil-mode, so don’t stress about that.

      • folkrav@lemmy.ca
        7·
        6 months ago

        Tramp is more featured, but if all one cares about is being able to edit remote files using a local editor, vim can edit remote files with scp too: scp://user@server[:port]//remote/file.txt

        I tried tramp-mode at some point, but I seem to remember some gotchas with LSP and pretty bleh latency, which didn’t make it all that useful to me… But I admittedly didn’t spend much time in emacs land.

    • Bo7a@lemmy.ca
      3·
      6 months ago

      Fair. But to a sysadmin or devops engineer availability is pretty important.

  • Lettuce eat lettuce@lemmy.ml
    8·
    6 months ago

    I plan on moving to a nice Neovim setup eventually, but VSCodium is so convenient out of the box for a baby developer like me.

    • Integrate777@discuss.online
      3·
      6 months ago

      You’ll be glad to know that the difficulty comes from the syntax and very little from any programming skill level. You learn new ways of writing certain code structures like indented curly braces for example. Programming python might be easier than cpp in vim, not due to the language, but just cpp having more complex syntax to type.

      Tldr, almost exactly the same amount of effort whether you’ve been coding for two weeks or two years.

  • muse@lemmy.blahaj.zone
    6·
    6 months ago

    That can’t be right, the red car has a service manual and too many functioning assemblies for it to be VS.

    • MajorHavoc@programming.dev
      2·
      6 months ago

      Nah. As a die hard Vim user, I can explain all day long why a flexible shared common editing experience across a team is a great idea, and why VSCodium is the obvious choice.

      And I’ll explain and agree in principle all day long from the familiar beloved comfort of my Vim editor.

  • Lovable Sidekick@lemmy.worldEnglish
    2·
    6 months ago

    I don’t mind Vim, it reminds me of my years using EDT on Vax/VMS systems in the 80s and 90s. My fingers knew all the function keys so well, the UI was almost invisible. But more recent years of using Windows because of work have ingrained VS and VSCode the same way, and I like the feel of the mouse.