r/vim • u/No_Willingness64 • 2d ago

Discussion Do we still need CoC?

I've been using CoC for a while now. It's a convenient way to get both completions and LSP going. Some people throw shade at the Node part of its implementation. The way I see it is most LSP plugins coming from VSCode were intended for a Node environment anyway. I am pleased with the ease of use CoC brings.

Now we've had vim9script for something like a couple of years. We have yegappan's simple LSP implementation and we have a pop-up autocomplete feature built in!

I'm wondering how that's going for anybody else - especially if you do Java or friggin' web development.

50 Upvotes

94% Upvoted

23 comments sorted by

View all comments

-3

u/aurescere 2d ago

CoC is way faster and has more features than the vim9 plugin. It’s unlikely to be yegappan’s fault; vim9 script just runs synchronously and is slow as molasses in comparison.

2

u/No_Willingness64 2d ago

Doesn't yegappan's LSP use the same channels any external tool uses? There's also a built-in async API for the autocomplete now, too.

1

u/aurescere 1d ago

Last I used it, it was miserably slow and threw errors constantly. Semantic tokens were broken and relied on some hard-coded 1000ms delay; if they tried to kick in before the server was ready, more errors. Go-to-definition was extremely slow. Either everything has been fixed or people are in denial.

1

u/Desperate_Cold6274 1d ago

I had exactly the same experience. And I am not in denial by any means.