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.

  • Aurenkin@sh.itjust.works
    link
    fedilink
    arrow-up
    1
    ·
    14 days ago

    Welcome, friend! I mostly use JVM languages at work these days which makes me sad because Neovim isn’t so great for them. It really is such a great editor though. It’s great fun seeing how people customise it as well.

    • ad_on_is@lemm.eeOP
      link
      fedilink
      English
      arrow-up
      2
      ·
      14 days ago

      Lol… I also spent the last week in customizing, going throuh almost all distros, until I found LazyVim to be the most vanilla one, with sane defaults and a great documentation.

      • moseschrute@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        14 days ago

        I’m using LunarVim, but LazyVim looks similar. I wonder how they compare. I found LunarVim to be a good starting point, but I’ve customized it quite a bit at this point.

        • ad_on_is@lemm.eeOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          14 days ago

          For me, LunarVim feels more like NVChad, with it’s own set of options to control neovim… I’m honestly not a huge fan of this approach.

          lvim.builtin.lualine.sections.lualine_c = {...}

          I prefer the “lazy” way using plugin files, with the lazy notation, since it feels more agnostic.