Comment by alexjplant
5 days ago
Ruby is only just now getting static typing and Rails has a lot of "magic" as part of its value prop. If you're trying to launch something of low to medium complexity quickly and stay on the happy path of the tools in the ecosystem then it works great. The lack of rigor from dynamic typing and latitude afforded by Ruby's expressive syntax can quickly become a footgun though.
My pet theory is that LLM coding is going to give the upper hand to more verbose languages like Golang or Typescript because more of the execution flow will end up explicitly in the LLM's context. Convention over configuration-type frameworks ruled when one-person code bulldozers shipped MVPs but Continue is upending this paradigm.
I wouldn't really call it a pet theory at this point; HN's front page daily further shows that LLMs suck at magic and excel at boring code, seeming quite immune to boredom. But I would argue what makes the difference for LLMs is not verbosity but locality, whether syntactic or analytical ie whether the type is just written here or you have an LSP server to query for it, the distinction is, being able to point to an arbitrary symbol and get lots of rich context about it.
It's a game changer for human devs also, and not really one I would expect a serious Rails habitué to necessarily evaluate in a way that's reliable. What did someone call that once, the "Blub Paradox?" Silly name, but that's this industry for you.