mason.nvim

As well as its own plugins Vim/NeoVim can use VSCode's LSPs, DAPs and extensions either directly or via plugins like CoC[1] and Mason[2]. I would be surprised if emacs couldn't do the same. 1. https://github.com/neoclide/coc.nvim 2. https://github.com/williamboman/mason.nvim

> No, the main difference is in the quality of plugins, not in how many there are. I don't think that is true. If you browse the vscode marketplace and search e.g. for python [1] you literally get hundreds of plugins. If you scroll down only a bit, you quickly end up at plugins that only have a few hundred to a few ten downloads. I highly doubt that the quality of those plugins is better than the plugins for (neo)vim. For your Rust-Analyzer Plugin example: I can install Rust-Analyzer with Mason in a few seconds as well and then (if you have lsp-zero [3] installed) it also just works™. But I agree, keeping a vim configuration up to date is akin to a hobby (which I by the way enjoy quite bit). [1] https://marketplace.visualstudio.com/search?term=python&targ... [2] https://github.com/williamboman/mason.nvim [3] https://github.com/VonHeikemen

There is also mason for installing LSP servers, DAP adapters, formatters and linters. https://github.com/williamboman/mason.nvim

FWIU coc.vim works with vim and nvim and works with VSCode LSP support: https://github.com/neoclide/coc.nvim There are many LSP implementations: https://langserver.org/ awesome-neovim Ctrl-F "DAP": https://github.com/rockerBOO/awesome-neovim#lsp mason.nvim: https://github.com/williamboman/mason.nvim : > Portable package manager for Neovim that runs everywhere Neovim runs. Easily install and manage LSP servers, DAP servers, linters, and formatters. conda-forge DAP: Debug Adapter Protocol https://microsoft.github.io/debug-adapter-protocol/implement...

There's also a Mason[0] plugin that handles the installation of LSP (also DAP/linters/formatters) installation in a very visual way. [0] https://github.com/williamboman/mason.nvim

I use a lot of them, many specific to my work, but here are some of the ones that I think will most improve the quality of life for most developers. - For a plug-in manager I user packer - For file/text search I recommend telescope (https://github.com/nvim-telescope/telescope.nvim) - Copilot (https://github.com/github/copilot.vim) - Nerd tree for file browsing (https://github.com/preservim/nerdtree) - commentary for commenting (https://github.com/tpope/vim-commentary) - ALE for linting (https://github.com/dense-analysis/ale) - Mason for installing LSP servers (https://github.com/williamboman/mason.nvim) Once you have the proper tooling in place you can do pretty much everything in vim that you are doing in vs code or intelliJ. I've just started using it for most of my dev work recently and I have found ThePrimeagen's youtube videos on vim

I use neovim. The plugin system has really grown. * I use Packer for plug-in managment: https://github.com/wbthomason/packer.nvim * I use Mason to install LSPs, linters and formatters: https://github.com/williamboman/mason.nvim * I use nvim-treesitter for better highlighting: https://github.com/nvim-treesitter/nvim-treesitter

While I was going through the effort to set up DAP support, I discovered [mason.nvim](https://github.com/williamboman/mason.nvim) which has been a game-changer for LSP, DAP, and linter setups. There had previously been fragmented plugins (williamboman/nvim-lsp-installer was Mason's predecessor and is a good example) that solved the problem of installation and management for each of these. With Mason, I feel that the story for managing different language environments has jumped to be extremely close to VSCode's extensions.