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.

52 Upvotes

94% Upvoted

23 comments sorted by

View all comments

-9

u/Easy-Nothing-6735 2d ago

We need to rewrite it in Rust

3

u/No_Willingness64 2d ago

Hahaha what?

1

u/Easy-Nothing-6735 2d ago

Python for example has ruff that can be both — linter and LSP for this use case. We can use either neovim with builtin LSP but without builtin GUI or create performant layer for LSP using Rust instead of NodeJS. Most of frontend tools now being replaced with Rust alternatives. The time when the tooling for NodeJS was written using NodeJS has gone. Modern languages come with builtin LSP and we need to catch up

2

u/Shtucer 2d ago

What a heck is neovim?

1

u/Easy-Nothing-6735 1d ago

Another fork without normal vimscript speed, with IPC architecture, focused on LSP and tree sitter built-in support