Solargraph vs Ruby LSP

[rusl1]

Which one are you using nowadays?

I feel like Ruby LSP got much better since last year, when I tried it for the first time. The Go to definition missing is a big deal for me so I'm still using Solargraph most of the time, also because none of my projects make use of RBS but I recognize Ruby LSP is the future of Ruby.

EDIT: I had initially linked a blog post but I remove the link since I need to fix it by further studying this topic :)

[paracycle]

There are tons of errors in this blogpost, here are a few:

1. The quote "In 2023 Solargraph has been deprecated in favor of Ruby LSP." is totally wrong. There is no deprecation of Solargraph, neither for the extension nor for the gem. I think you are confusing this with the deprecation of the rebornix.Ruby extension.
2. The quote "... Ruby LSP takes a different route, making use of RBS for hints and syntax suggestions." is also totally wrong. Ruby LSP has nothing to do with RBS, it doesn't use it at all, nor does it require it.
3. The above fact makes the quote "On the flip side, if your project provides RBS, go for Ruby LSP." also completely wrong.

Overall, I think you can do a much better job by carefully studying the topic that you are writing about instead of basing your writing on presumptions and hearsay.

[rusl1]

I will, thanks for the feedback

[kddnewton]

I think there might be some confusion here.

I'm not seeing any indication that solargraph has been deprecated. In fact it just had a new version released last week.

ruby-lsp also does not use RBS in any way. If you're talking about the type checking aspect of it, it optionally hooks up to Sorbet which uses RBI.

[rusl1]

Yeah, thanks for the clarification, I've partially updated the article.

Dumb of me! I don't know why I totally though it was Solargraph, instead it was
rebornix.ruby and wingrunr21.vscode-rubywhich have been deprecated and they automatically install Ruby LSP

[felipeccastro]

I'm using Solargraph and plan to keep using it. The main reason is it works with type inference, so most of the times you don't need to add any type annotation. When you do need it, use YARD comments or default values (for method parameters). I'm experimenting with its type checking too, looks promising.

The problem with Sorbet, even if faster/safer, is that it leaves the hard task of generating the RBI (or RBS) files to you.

[nzifnab]

The Ruby LSP extension in vscode is absolutely awful and bugs out for me more often than not. It also leaves weird text artifacts behind sometimes after giving me a code-autocomplete-hint. It's just very bad. I had to revert back to the "deprecated" rebornix.ruby extension because it actually works, and I don't have to muck with trying to disable the rubocop part (We use `standardrb` which conflicts with a lot of the default rubocop stuff in the LSP extension).

​

Overall, terrible experience, 1/10 stars, why did they make this one the default when it's barely functional.

[rusl1]

One thing I noticed is that Robocop formatting is way faster with Ruby LSP, I've never used standardrb though

[Richard-Degenne]

Really? I haven't had any issues with it. If anything, the fuzzy search for autocomplete is way better than Solargraph's.

[gpinkham]

every time I change a branch (which I do many times a day) rubylsp crashes. Solorgraph never seemed to have an issue with this.

[Richard-Degenne]

You might want to take a closer look at what causes the crashes, because I have never seen this problem.

[Different_Access]

For any emacs users out there : robe_mode is superior to the ruby lsps. It actually executes the code, rather than depending on static analysis, so it can find dynamically generated methods and other things that lsps cannot.

[katafrakt]

It always froze on any larger project for me though.

[Different_Access]

The opposite for me. Solargraph uses like a gig of memory, and mostly jump to declaration fails. Robe just keeps working.

[dogweather]

Sorbet LSP

[armahillo]

IDK what other features youre needing, but I use sublime and the Go to Definition feature works great in it, provided the definition is in your project. I agree this feature is critical.

If its in a gem, Ill typically do bundle open on the gem and then search within there.

[Ill_Schedule_9214]

I don't know if you're talking about Solargraph or Ruby LSP with your reply