Returning to Rails in 2026

Original Article ↗ Hacker News Discussion ↗

Rails’ New AI/Agent Positioning

  • Homepage slogan about “accelerating agents” and “token-efficient code” is widely seen as cringey, confusing, and misrepresentative of Rails’ core value.
  • Some argue it’s savvy marketing/positioning for an “agentic coding” world and that convention-over-configuration does help coding agents.
  • Others counter that agents already learn conventions from corpora and the pitch should focus on humans, not LLMs.

Rails vs JS/TypeScript and Typing

  • Many commenters now consider static typing (especially TypeScript) essential for large or long-lived systems and for LLM-assisted workflows.
  • TypeScript is praised for a powerful, expressive, “AI-friendly” type system; Go, Rust, Haskell, C#, Java are also mentioned with tradeoffs.
  • Ruby’s RBS/Steep/Sorbet are acknowledged but often viewed as less mature or less ergonomic; some say they remove much of Ruby’s “fun.”
  • Several refuse to work on untyped codebases again; others report success with Sorbet and good tooling.

Developer Experience, Scope, and Longevity

  • Strong praise for Rails as a “one-person framework”: batteries included, coherent ecosystem, clear MVC structure, and high productivity for CRUD/SaaS-style apps.
  • Long-running production Rails apps (10–20 years) reported as viable, with relatively smooth upgrades compared to disruptive JS/Next.js shifts.
  • Some returning users feel modern Rails is larger, more complex, and less “obvious” than pre‑3/4 versions; generators now create many files and Kamal/docs can feel confusing.
  • Counterpoint: Rails 7/8 said to be less “magic,” with saner JS handling and improved upgrade story.

Security and Conventions vs JS Ecosystem

  • Rails/Laravel praised for opinionated structure, ORM defaults, and built-in protections (CSRF, SQL injection avoidance via proper DB APIs).
  • JS stacks (Next, React, etc.) criticized for loose conventions, fragmented tooling, and frequent real-world security issues when teams “vibe code.”
  • Some mention JS MVC-style frameworks (NestJS, AdonisJS) and focused TS stacks (e.g., oRPC + Drizzle) as partial answers.

Elixir/Phoenix and Other Alternatives

  • Elixir/Phoenix repeatedly recommended as a modern, functional “spiritual successor”: BEAM concurrency, clear dataflow, LiveView for rich UIs, and robust long-lived apps.
  • Downsides noted: smaller job market, fewer libraries, trickier distribution for some use cases.
  • Other mentions: Symfony, Django, Laravel, Go, Rust/Loco, and TS-first frameworks as options depending on problem shape.

Popularity, “Death,” and AI Era

  • Some insist Ruby/Rails are in long-term decline (survey rankings, aging/abandoned gems, shrinking community).
  • Others counter with sustained production use, high satisfaction, and survey categories where Rails remains desired.
  • Debate on whether languages/frameworks matter less with LLMs; some say agents make any stack fine, others argue conventions and types still matter greatly.