• lime!@feddit.nuEnglish
      0·
      3 months ago

      vis is such a neat idea, i followed it years ago. any good plugins yet? i really love the structural regex workflow but since kakoune/helix hijacked my muscle memory i would need more support for external tools to go full vis…

      • m4m4m4m4@lemmy.world
        0·
        3 months ago

        The thing about good plugins is relative - I just have vis-pairs, but I am not a seasoned developer (I’m not even a formal developer/CS person, just a graphic designer doing frontend and a tiny bit of backend!) so I don’t really miss anything else. vis’ phylosophy relies on the unix-as-ide concept, though. Still I do know that there is stuff like a LSP plugin.

        What I really miss from vim is buffers. vis still does not have a client/server feature so you still have to rely in its allegedly temporary split panes kinda solution. It seems vis’ main developer got some personal issues going on so volunteers are doing some little changes here and there but with so few manpower it doesn’t seem like those needed big changes are happening anytime soon. Hence why I’m trying to spread its gospel in hopes to get people interested in contributing to it.

  • Lettuce eat lettuce@lemmy.ml
    0·
    3 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
      0·
      3 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.

  • 🦄🦄🦄@feddit.org
    0·
    3 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).

    • Bo7a@lemmy.ca
      0·
      3 months ago

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

    • CubitOom@infosec.pubEnglish
      0·
      3 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.

      • calcopiritus@lemmy.world
        0·
        3 months ago

        You can do that with vscode too. And probably many IDEs.

        The only real reason for which you would need to use vim in such cases is if the target computer can’t run the vscode server, which I’ve never encountered yet.

        • CubitOom@infosec.pubEnglish
          0·
          3 months ago

          I’m talking about not needing anything installed on the server though. Like you don’t need sudo. If the server has ssh then you can use Emacs to edit a file on it

          • calcopiritus@lemmy.world
            0·
            3 months ago

            Don’t need sudo or anything pre installed for vscode either. It will send the server to the machine via SSH and then run it automagically.

      • folkrav@lemmy.ca
        0·
        3 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.

    • toynbee@lemmy.world
      0·
      3 months ago

      I’ve been a 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.

    • AntY@lemmy.world
      0·
      3 months ago

      Vim is a way more competent editor than nano. If you spend a lot of time editing files via ssh, vim is amazing. And when you get bitten by it, you’re infected. ;-)

  • Abnorc@lemm.ee
    0·
    3 months ago

    I feel like I need to learn VIM at some point because various system tools have a habit of using it. (rpmrebuild and the man pages come to mind) It just comes up here and there even if you don’t care for it.

  • HStone32@lemmy.world
    0·
    3 months ago

    The amount of time my classmates have spent dealing with vscode crashing, freezing, breaking, etc is way beyond negligible. And yet, I’m the weird guy apparently for preferring vim and GCC.

  • LovableSidekick@lemmy.worldEnglish
    0·
    3 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.

  • dejected_warp_core@lemmy.world
    0·
    3 months ago

    I would argue that vim is fantastic for a lot of editing and coding tasks, just not all of them.

    Where it utterly fails is with deep trees of files in codebases, like you see in Java or some Javascript/Typescript apps. Even with a robust suite of add-ons, you wind up backing into full-bore IDE territory to manage that much filesystem complexity. Only difference is that navigating and managing a large file tree w/o a mouse is kind of torture.

    • expr@programming.dev
      0·
      3 months ago

      File-based navigation is often inefficient anyway (symbolic navigation is much better when you can), but if you do need it, that’s what fuzzy finders are for. Blows any mouse-based navigation out of the water.

      The only time a visual structure is useful is when you are actually just interested in learning how things are structured for whatever reason, but for that task, tree works just fine anyway.

    • murtaza64@programming.dev
      0·
      3 months ago

      Once I got used to single-directory filetree browsing plus fuzzy finding, I have never been able to comfortably use a traditional filetree anymore. most of them are not designed for efficient keyboard use (vscode and intellij at least) and don’t really help understanding the structure of the project imo (unless there arent that many files). For massive projects I find it easier to spend the initial effort of learning a few directory names and the vague structure using oil.nvim, and then eventually I can just find what I need almost instantly by fuzzy finding.

    • ivn@jlai.lu
      0·
      3 months ago

      Fuzzy finding really shine for this use case, no need for a mouse.

  • Bysmuth@lemmy.zipEnglish
    0·
    3 months ago

    Code and intellij have plugins available to use vim keybindings on them. I like this approach to get the best of both worlds

      • stetech@lemmy.world
        0·
        3 months ago

        To you, @[email protected], and anyone else planning to do the switch:

        Back when I was still a VSC(odium) user, you needed to perform a small tweak to regain access to the quite useful extensions marketplace (in the sense of, paste the extension ID, see the same results as a M$ VSCode user*): There is a file named product.json which allows you to “regain” access if you populate it with the following values:

        {
  "extensionsGallery": {
    "serviceUrl": "https://marketplace.visualstudio.com/_apis/public/gallery",
    "itemUrl": "https://marketplace.visualstudio.com/items",
    "cacheUrl": "https://vscode.blob.core.windows.net/gallery/index",
    "controlUrl": ""
  }
}

        (Taken from my old dotfiles, so this may be outdated, not sure. Also, you’ll have to look up the location of this file, it will differ depending on OS. On macOS it goes in ~/Library/Application Support/VSCodium.)

        *If you do not need this 1:1 identical functionality, you may try the Open VSX marketplace. But especially in a class setting, I found this very useful, since all the tutorials/instructions will work without needing adaptation.

  • phoneymouse@lemmy.world
    0·
    3 months ago

    My professor was always trying to get us to use vim or eMacs over an IDE to write our C programs. I’m sorry, I like using a mouse. I know, I know, blasphemy. I’m taking a shortcut. I’m a noob.

    When I absolutely have to, I go for vim, mostly because I know a few of the key bindings for it, but otherwise avoid it.

    • BaumGeist@lemmy.ml
      0·
      3 months ago

      I’m taking a shortcut

      more like a longcut. I save so much time and effort not having to switch my right hand between the mouse and keyboard constantly

      • phoneymouse@lemmy.world
        0·
        3 months ago

        I keep my hands on my laptop and use my thumb on the track pad. My hands don’t leave the keyboard. I actually never use extra mice or extra keyboards.

    • MajorHavoc@programming.dev
      0·
      3 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.