• phoneymouse@lemmy.world
    link
    fedilink
    arrow-up
    6
    ·
    edit-2
    5 hours 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
      link
      fedilink
      arrow-up
      2
      ·
      5 hours 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
        link
        fedilink
        arrow-up
        4
        ·
        5 hours 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.

        • BaumGeist@lemmy.ml
          link
          fedilink
          arrow-up
          4
          ·
          5 hours ago

          track pad

          it’s okay, we’re gonna make a plan and get you to safety. Pretend you’re ordering a pizza. How many people are currently holding you captive?

  • LovableSidekick@lemmy.world
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    5 hours 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.

  • muse@lemmy.blahaj.zone
    link
    fedilink
    arrow-up
    7
    ·
    edit-2
    10 hours ago

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

  • udon@lemmy.world
    link
    fedilink
    arrow-up
    18
    ·
    20 hours 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.ca
      link
      fedilink
      English
      arrow-up
      3
      arrow-down
      1
      ·
      edit-2
      11 hours ago

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

  • dejected_warp_core@lemmy.world
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    17 hours 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.

    • ivn@jlai.lu
      link
      fedilink
      arrow-up
      11
      ·
      16 hours ago

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

    • expr@programming.dev
      link
      fedilink
      arrow-up
      2
      ·
      13 hours 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
      link
      fedilink
      arrow-up
      4
      ·
      16 hours 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.

  • Lettuce eat lettuce@lemmy.ml
    link
    fedilink
    arrow-up
    11
    ·
    20 hours 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
      link
      fedilink
      arrow-up
      5
      ·
      edit-2
      19 hours 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.