nvim-ale-diagnostic VS ddc.vim

I did find nathanmsmith/nvim-ale-diagnostic but it is abandoned; and I'm not sure if it accomplishes what I want.

I didn't replace it, but started using https://github.com/nathanmsmith/nvim-ale-diagnostic instead. With a few tweaks works quite well, but long term I'm planning to move to null-ls and/or efm.

My current setup is: use ale for linting and formatting with https://github.com/nathunsmitty/nvim-ale-diagnostic to send lsp diagnostics to it.

To use it with nvim-lsp you will need nvim-ale-diagnostic

I just use this plugin and toggle ALE itself.

for folks who are on nvim-lsp there is a similar plugin nvim-ale-diagnostic

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.