Honestly… everybody should try out neovim for at least a week. I mean like… fully commit to it.

It’s just amazing how fast and light on resource usage it is, compared to vscode.

For reference: I just opened qmk_firmware which has a shit load of clang code and files. Guess what, neovim doesn’t even break a sweat, while vscode almost burns my CPU.

  • CheesyFox@lemmy.sdf.org
    6·
    13 days ago

    tried it. Now i have ptsd after attempting to config it. that’s why i use helix, seems to work best with minimal configuration. Kakoune makes the most sence out of its keybind paradigm tho

    • zygo_histo_morpheus@programming.dev
      1·
      12 days ago

      Out of curiosity, what have you had trouble with config wise? I’ve been using vm/neovim for long enough that I can’t relate to the setting up for the first time process anymore. Is it basic stuff or things like adding lsp?

      Helix does come with more bells and whistles out of the box so it’s great if you don’t feel like tinkering with your setup. Couldn’t be me, I love that shit!

      • CheesyFox@lemmy.sdf.org
        3·
        12 days ago

        I was dumb and spoiled by vscode, i wanted to integrate a task runner and a debugger. They both worked kinda shitty compared to what vscode does and i disliked how bloated the config was. Now i simply use GDB as the debugger and Just as the task runner, stickitg to helix more because of the keybinds, integrated tree sitter and other stuff.

        I also love to tinker the environment i work in to my liking (love me my gruvbox hyprland), but i’m kinda not a fan of doing everything from scratch, and pre-made configs for nvim either give me agoraphobia by how huge they are, or are too barebones. Helix just clicked for me, because it offers everything necessary out of the box, while allowing to tailor the rest to your liking. Also, because of its editing model which is supperior.

        • zygo_histo_morpheus@programming.dev
          2·
          12 days ago

          Debugging is kind of a weak point in vim to be honest, there is a plugin called termdebug which comes bundled with vim that can do gdb debugging ok, but anything more complicated mostly just feels like a lot more work and a bit more jank than just using vscode.

          I use just as well, it’s a more vimy approach than something more tightly integrated so that makes sense.

          Helix is nice, but I don’t think I could leave behind some of my vim plugins, fugitive in particular is an integral part of my git workflow. Haven’t used the kakoune editing model enough to really decide if I think it’s better than vim personally.