• @[email protected]
    link
    fedilink
    1311 months ago

    I mean, I’d just bind vim to nvim. If you still want vim accessible, bind it to something else. I don’t really see any downsides to Neovim: it’s decently backwards compatible, enough to use most old plugins, with the advantages of Lua config and a much wider repository of plugins.

    • @WalrusByte
      link
      English
      211 months ago

      I did bind it, but it still had a few annoyances (that I no longer remember what they are because it was a few years ago). I couldn’t really find a reason for me to use it other than people recommending it. I guess my use case is a bit different from theirs or something. Either way, I’m used to regular Vim now, so I don’t care to switch

      • @[email protected]
        link
        fedilink
        311 months ago

        That’s fair. I started with what everyone was using at the time, which just so happened to be Neovim. I’m also too lazy to switch/try anything else.

        Plus, I’m not sure if Neovim simply extends Vim functionality. I know it’s a fork, but the codebase has changed so much I’m pretty sure many newer features of Vim need to be manually added to Neovim. Inlay hints in the middle of lines is already implemented in Vim: as for Neovim, it’s not here yet (well, it’s coming in 0.10, but I don’t use nightly so I don’t have it)

        • @WalrusByte
          link
          English
          111 months ago

          The biggest difference that I know of is Neovim uses Lua instead of Vimscript for plugins. I’m sure there’s some other stuff tacked on but idk what haha