Our great sponsors
-
mini.nvim
Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
mason.nvim
Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters.
-
-
-
-
coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
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.
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.
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.
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.
Not the OP but I also do that. https://github.com/ghostbuster91/dot-files