What's next for Coc.nvim?

[jackielii]

Hello everyone,

As a huge fan of Coc.nvim, I'm eager to see it being enjoyed by more people and
continuously improved, despite facing competition from built-in LSP clients
inside Neovim.

People may want "small" components to have composability and control over
things, which is what the built-in LSP client is about. For some users out
there, it will work, but for the vast majority of us, being built-in doesn't
automatically make it good. The more moving parts there are, the easier it is to
break. I believe people are not necessarily against the "all-in-one" solution,
as long as it Just Works and still preserves the flexibility of Vim.

However, the more people use it, the faster it will improve. Coc.nvim should
find its niche and bet on it. One of such niche is the ability of porting VSCode
plugins to Coc.nvim, the accessibility to the vast (still growing) amount of
VSCode plugins is a huge upside. Enabling the "Easy Adaptation" of these plugins
would be a great feature for many users. While I see efforts being made in this
area, such as the pull request found here
(#3713), it has yet to be completed. In
an ideal world, wrapping an existing VSCode plugin to make it a Coc.nvim plugin
would be possible. While this may not be feasible in reality, it could be a
valuable direction to explore.

For those who are currently using VSCode, Coc.nvim should provide a seamless
transition into the Vim world without having to sacrifice the functionality and
features they've come to rely on. By offering accessibility to a vast array of
VSCode plugins and enabling easy adaptation of these plugins, Coc.nvim makes it
easier for VSCode users to switch to Vim while still being able to use the
plugins they're already familiar with. This way, they can enjoy the speed and
efficiency of Vim without giving up the tools they rely on.

For those who are already familiar with Vim, Coc.nvim is well-positioned to
offer them a reliable and efficient LSP client. In addition, they can tap into
the VSCode world, especially considering that many of the AI plugins are
released on VSCode first. You don't want to miss the AI train, right?

In summary, Coc.nvim is attracting both VSCode users looking to improve their
editing skills by learning Vim, as well as Vim users seeking to tap into the
VSCode world.

[hexh250786313]

I understand you. Being able to porting VSCode plugins to Coc is still the most important reason why I insist on using Coc. In fact, the huge VSCode community is one of the supports for Coc's sustainable development in the future.

[chemzqm]

Yes, we need AI plugins for vim.

[luisdavim]

I think that more important than AI it would be improving the UX around Debugging, doing for DAP what coc already did for LSP, making it super easy to setup and make it work out of the box.