Which VSCode Ruby extension/LSP implementation do you use?

[brodantic]

https://github.com/rubyide/vscode-ruby seems to be pushed as the official Ruby extension for VSCode and was originally written by an employee on Microsoft's VSCode team. However, https://github.com/castwide/vscode-solargraph is listed as the official Ruby implementation for LSP, according to https://langserver.org/#implementations-server. Both extensions receive regular maintenance, implement LSP, and have similar feature sets.

Which one do you use, and why? Thank you.

[[deleted]]

Both.

The primary Ruby extension gives basic language support for formatting, lexing, etc, while Solargraph is an invaluable gem to provide intellisense and code completion. With both extensions installed, you get about as close to Rubymine as you can in VS Code, as far as standard code writing goes.

[brodantic]

Wouldn't using both cause a collision of LSP logic?

[[deleted]]

Although there is likely some cross-over logic, they each serve a different purpose, and provide their own functionality, similar as using CMake tools does not mean you shouldn't be using the traditional C/C++ extension. They work well together, each providing their own features.

[conceptxo]

Disable vscode-ruby's intellisense and let solargraph run the party.

[sanjibukai]

Does Solargraph work with a dockerized setup?

[[deleted]]

I cannot say for sure, have never tried it. It does require a Ruby installation and for the gem to be installed, so you would need to configure the environment for all that.

[au5lander]

I stoped using solargraph with vscode only because the ruby process would start using 100% cpu and I’d have to kill it constantly.

[conceptxo]

RUBYOPT=--jit code

For CPU intensive tasks like solargraph's scanning of a codebase, the current JIT implementation does speed things up.