←back to thread

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

(railsatscale.com)
140 points ksec | 3 comments | 24 Jul 24 15:30 UTC | HN request time: 0s | source
Show context
stevebmark ◴[27 Jul 24 04:27 UTC] No.41084461[source]▶
Ruby has a lot going for it, but as other commenters point out, the metaprogramming nightmares of the language have held it back 10-30 years behind modern language ecosystems, depending on the feature you're looking at. Celebrating "jump to source definition" (sometimes working) for such a mature language is a symptom of the nature of the language. Sometimes insane dynamic freedom is really useful, but it comes with heavy drawbacks.
replies(4): >>41085027 #>>41085047 #>>41086943 #>>41092303 #
1. eduction ◴[27 Jul 24 14:47 UTC] No.41086943[source]▶
I’m very curious how a language that’s not yet 29 years old can be held back 30 years.
replies(1): >>41086957 #
2. sapiogram ◴[27 Jul 24 14:49 UTC] No.41086957[source]▶
Makes perfect sense to me, it just means the language was already a year behind when it launched.
replies(1): >>41125884 #
3. brigandish ◴[01 Aug 24 03:30 UTC] No.41125884[source]▶
Which languages were ahead at that point? Haskell started in 1990, so was it only a year ahead after 5 years in existence but since then it has gone 30 years ahead and Ruby hasn’t moved forward at all, or is has it gone 30 years into Ruby’s future after another 30 years?

Or is it that the original comment showed no knowledge of programming language history? It’s a tough choice!