• @joojmachineOP
    link
    43 years ago

    In my case it was just a procrastination project anyways, I used nvim through NvChad for a long while.

    I switched to VSCode due to the ease to install extensions and language related stuff, but it never felt quite right, specially the UI. It had a lot of stuff that bugged me and it felt a little overwhelming for me, considering I’m still a beginner when it comes to development. Also even though memory usage isn’t an issue for me, seeing a code editor using over 300MB of RAM was just sad to see. So I decided to come back. Stupid reasons, I know.

    But, since I was already doing so, I thought it was a fun project to try to rewrite my old init.vim as much as I could in lua (even though I know nothing of Lua lol), and in the end I managed to do so (and it turned out pretty well, I’d say), so hurray.

    • Tmpod
      link
      fedilink
      23 years ago

      Stupid reasons, I know.

      Not at all lol. I really like the highly configurable feel of (neo)vim, the nice community around it, with its many plugins, and ofc the vim-style workflow. Not eating up my computer’s resources (even though it is a quite powerful laptop) is important to me, not only because it is indeed sad to see such consumption, but also because that consumption drain battery faster.

      and in the end I managed to do so (and it turned out pretty well, I’d say), so hurray.

      It does look good indeed! I had a wrong (most likely outdated) idea of the Lua API, but I have to say it is rather nice looking :P
      Might consider something like this, idk. This API is certainly pretty interesting, and I think neovim hit quite the spot with having it, because now you can have plugins that really benefit from a language that works really well for this purpose and an existing ecosystem of interpreters, runtimes, packages, etc. Stuff like telescope.vim (which is just amazing) wouldn’t be possible, or at least pretty unfeasible, with just vimscript.