←back to thread

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

(railsatscale.com)
140 points ksec | 1 comments | 24 Jul 24 15:30 UTC | HN request time: 0.319s | 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. cardy31 ◴[27 Jul 24 02:35 UTC] No.41084088[source]▶
Not everyone is at a point where they are greenfield picking a language for a new project. Sorbet was built by a large organization (Stripe IIRC) and is used effectively by organizations with large Rails codebases. I think Sorbet is a great way to maintain velocity on a large Ruby codebase after the initial velocity benefits of dynamic typing have ceased and the dynamic typing is actually a drain on velocity.