• dustyData@lemmy.world
    link
    fedilink
    arrow-up
    10
    arrow-down
    4
    ·
    8 months ago

    You could either spend hundreds of hours being a slower programmer in order to learn something that squeezes a diminishing returns save on time. Or you can be a fast programmer now, albeit marginally slower than one that knows vim.

    • KrankyKong@lemmy.world
      link
      fedilink
      arrow-up
      14
      ·
      edit-2
      8 months ago

      Any amount of time I’ve saved using neovim has easily been offset by the amount of time I’ve spent configuring it. Wouldn’t change it though. It’s just fun to use, and there’s something nice about using an editor that I configured from the ground up. You can also just use a neovim distribution if you don’t care to set it up yourself.

      The keybindings aren’t hard though, and I would say that learning vim keybindings has had a net positive impact on my efficiency overall. They become second nature more quickly than you would think. Most actions are muscle memory at this point. Maybe a week of frustration, then you’ll be back up to speed. Then you get faster and more fluid from there.

      • dukk@programming.dev
        link
        fedilink
        arrow-up
        2
        ·
        8 months ago

        Maybe I’m just lazy, I’ve only invested 10-15 hours total into my config.

        Once I got it working, I’ve never bothered to really even touch it. (I probably should, it’s most likely months of out of date…just like my NixOS config…)

        Next time I make changes will probably be when I update to 0.10 for inlay hints and set that up along with attempting to fix that error message that randomly pops up every time I start Neovim.

        Also probably not the typical Neovim config experience, but I’ve configured it enough to get of my way, now I just want to write code.