lasse16
commented
2 years ago Done and dusted. I felt the need to revisit this issue given the recent release of vim9script.
I switched to Neovim ages ago, and my dev environment is set up; At least to a bearable standard :) ; My config is already in lua, so there is no way back, but given the reasons from the issue descriptions, I do not look back either.
As a update on the mentioned plugins:
- LSP setup is complete
- Treesitter is enabled and color scheme is set
- Did not try Fire-Nvim yet
- Switched to nvim-dap ( an LSP-like protocol for Debuggers )
I've been debating switching to neovim for quite some time now.
The conclusion is that I want to do this. Vims main advantage over neovim in my eyes is its ubiquity. Well that and the fact that I have it already setup. However I am no sys-admin, so it's rare for me to switch computers and do my setup multiple times. I use Vim more as a do-all editing environment, almost as an all-purpose IDE.
This seems to fit beeter with the Neovim mentality too. The support for newer features, like tree-sitter or Language server protocol, is faster and better in Neovim. At this point treee-sitter is not supported in Vim and LSPs are only supported via plugins. LSP is builtin in Neovim, and tree-sitter supported via a plugin.
Further, most of the online community seems to be switching too. So tutorial and video support is better for Neovim.
Learning Lua as a scripting language is also preferable over Vimscript.
Lots of good points for switching to Neovim, so I decided to do the switch.
Stuff to keep an eye on: