←back to thread

Mastering Ruby Code Navigation: Ruby LSP Enhancements in the First Half of 2024

(railsatscale.com)
140 points ksec | 2 comments | 24 Jul 24 15:30 UTC | HN request time: 0.482s | source
Show context
simply-typed ◴[27 Jul 24 01:40 UTC] No.41083880[source]▶
The fact IntelliSense and jump-to-source are supported at a very superficial level goes to show the heavy drawbacks of dynamic types.

Sorbet may fix things, but at that point, just use a language with more mature tooling around types, like Python or TypeScript.

Dynamic types offer dubious marginal benefits but bring tons of downsides. The demonstrations in this article reflect that.

replies(6): >>41083934 #>>41083947 #>>41084060 #>>41084088 #>>41084115 #>>41084491 #
1. viraptor ◴[27 Jul 24 04:39 UTC] No.41084491[source]▶
> Sorbet may fix things

Sorbet is very slow for large codebases. I keep checking it from time to time, but the biggest service I'm dealing with just fails to run through the initialisation. And that's ignoring the idea that someone will have to clean up the result. Not holding my breath for it to be functional in LSP situations.

replies(1): >>41085378 #
2. pawelduda ◴[27 Jul 24 09:11 UTC] No.41085378[source]▶
How large is large here? I'm using sorbet on fairly big project and it takes like 3 seconds to scan the entire codebase with "srb tc", and with their LSP in editor the diagnostics refresh almost immediately before I stop typing. That is, without even using Sorbet's cache