ddc.vim VS nvim-lsp-installer

Have a look at ddc.vim and denops.vim

There is shougo/ddc.vim by the same author

e.g:https://github.com/Shougo/ddc.vim

I use dense-analysis/Ale for code linting. Lately, I moved to update my tab completion from deoplete to Shougo/ddc.vim; the autocompletion of Ale is routed to ddc using statiolake/ddc-ale but the Ale autocomplete leaves things to be desired.

I was looking at ddc.vim and it looked somewhat similar to nvim-cmp. There's also multiple sources for it with no inbuilt ones. So, I was wondering if anyone has used both of them and could provide some pointers on a rough comparison between the both. Also, if there's any config file with sources for lsp, buffer, and other useful ones already setup, then could you share that too?

Sadly deoplete doesn't play well with 'some' asynchronous plugin sources (ex: vim-iced). I still got to try ddc.vim to see if things are easier and if middle word completion is done right.

I had previous gotten a working setup with https://github.com/williamboman/nvim-lsp-installer however, I have been unable to get it working ever since.

The only way to stay up to date, is when you read the commits if you update the plugins. In this case for the lsp-installer in the commit bfa74f4 was mentioned that the plugin will no longer maintained

A word of caution, I believe lspinstall has been deprecated in favor of nvim-lspinstall which itself has also been deprecated in favor of mason-lspconfig

We have now migrated from nvim-lsp-instasller to mason which provides automatic LSP and null-ls configuration after installation

nvim-lsp-installer or mason.nvim. FYI lsp-zero also uses mason.nvim for managing installation.

I'm using nvim-lsp-installer it installs typescript when installing volar. So I had given it that path. Plus I had typescript locally installing since I'm using vue3+ts(vite) template

Though mason only recently replaced nvim-lsp-installer. Same author but they decided to make a complete rewrite given the broader scope beyond only providing language servers. And nvim-dap had it's initial release in late July. The actual dap servers are all kind of mature since they've been running on vscode for a couple of years or more now - and the protocol is apparently almost as old as lsp. So when I call them beta, it's more a commentary on the state of the neovim side of the ecosystem. If you mess around getting nvim-dap to work then there's a chance things might change over the coming months and you might have to return to configuring it more often than you'd like. In this sense for now I'm happy just to open vscode or another more appropriate IDE to debug. But I can see myself using the plugins in a year or two when they've matured.

Here are a few resources to get you started: 1. https://github.com/neovim/nvim-lspconfig 1. https://github.com/golang/tools/tree/master/gopls 1. https://github.com/williamboman/nvim-lsp-installer

Can recommend a combination of omnisharp-roslyn native LSP (installed manually or through something like mason or nvim-lsp-installer) with omnisharp-vim for some extra C#-niceties like OmniSharpRunTest, etc.