Our great sponsors
-
Although I mostly agree with all the points, here are a couple more: - Probably the biggest frustrations come from the need to set up language support: LSP, treesitter, DAP, all of that. This point should be constantly vanishing, though, with tools like williamboman/mason.nvim and VonHeikemen/lsp-zero.nvim. - Another strategy for an easier transition is to use Vim emulation in your IDE of choice while using Neovim as the default editor of text files. This will make you more comfortable with Vim modal editing without much pressure. It was my path around 4-5 years ago. - Be willing to enjoy spending time learning and reading help pages.
-
mini.nvim
Library of 20+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort
Use mini.nvim unless you have a good reason not to. The mini plugins are easy to use and Just Work (TM). You probably don't need to copy paste hundreds of lines of Lua to get autocomplete working.
-
InfluxDB
Access the most powerful time series database as a service. Ingest, store, & analyze all types of time series data in a fully-managed, purpose-built database. Keep data forever with low-cost storage and superior data compression.
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
Although I mostly agree with all the points, here are a couple more: - Probably the biggest frustrations come from the need to set up language support: LSP, treesitter, DAP, all of that. This point should be constantly vanishing, though, with tools like williamboman/mason.nvim and VonHeikemen/lsp-zero.nvim. - Another strategy for an easier transition is to use Vim emulation in your IDE of choice while using Neovim as the default editor of text files. This will make you more comfortable with Vim modal editing without much pressure. It was my path around 4-5 years ago. - Be willing to enjoy spending time learning and reading help pages.
-
Mason is probably easier to use than Puppet, Chef, Ansible, etc. I use Nix: https://nixos.org/
-
As mentioned by others, there are now some tools that now help alleviate those problems (like https://github.com/VonHeikemen/lsp-zero.nvim) , however I still think debugging and DAP is painful for new users. Something like LspConfig for DAP or a similar simplified experience might help.
-
Just FYI, Using vscode-neovim you get a fully embedded instance of Neovim in Vscode, which is a much better experience compared to Vim emulation.
-
coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
The bit to me is that you need those tools and then you need to install whatever plugins provide all the non-spec LSP server features for the languages you're interested in, which is basically of course when you recognize that the LSP spec can't possibly resolve the difference in language tooling needs between, say, Java and Haskell. So off the bat you're creating this friction. For all its issues, coc.nvim gets the LSP UX story right, language tooling just tends to be wholemeal.
-
SonarLint
Clean code begins in your IDE with SonarLint. Up your coding game and discover issues early. SonarLint is a free plugin that helps you find & fix bugs and security issues from the moment you start writing code. Install from your favorite IDE marketplace today.
-
Not the OP but I also do that. https://github.com/ghostbuster91/dot-files
