Developers weigh Rails' proven productivity against the allure of a Rust rewrite.
RUBY ON RAILS STILL MAKES SENSE DESPITE RUST REWRITE HYPE
*Frameworks still deliver structure, security and free performance gains. LLMs accelerate updates but don’t erase the need for proven abstractions.*
On 18 Oct 2026 a developer asked whether Ruby on Rails still makes sense in an era where large language models can churn out code at near‑zero cost. The question cut to the heart of a growing debate: should teams abandon mature frameworks for low‑level languages like Rust, or lean on AI to keep legacy stacks alive? The author’s response is unequivocal – Rails remains relevant. He frames the issue around productivity, security and user experience, arguing that abstractions built over years cannot be dismissed simply because code can now be generated automatically.
Why frameworks still matter
The author argues that Rails, like any active framework, supplies structure, avoids reinventing the wheel, and rolls out security patches and performance improvements automatically. Those benefits persist regardless of how cheap code generation becomes. A framework’s predictable layout lets developers navigate, debug and extend projects with confidence. LLMs, trained on the same frameworks, inherit those patterns, so the underlying abstractions remain valuable. The piece stresses that abandoning a framework means losing the safety net of regular updates and community‑tested conventions.
Should developers rewrite Rails apps in Rust?
The source cautions against a wholesale Rust rewrite. While LLMs can translate code, each language and ecosystem carries unique design decisions. Switching forces developers to make choices they never faced before, potentially altering behavior that users rely on. The author notes that a Rust version might fix hidden bugs but could also introduce subtle new ones, especially in UI‑heavy products where users depend on quirks. Testing becomes extensive, and any change to pixels or icons sparks complaints. The risk‑reward balance leans toward preserving the existing stack unless performance gains are undeniable.
Can LLMs replace the need for a rewrite?
According to the author, LLMs excel at improving existing code without a full language swap. Prompting an LLM to “make it faster” can yield optimisations that keep the original behavior intact. Updating dependencies pulls in free security fixes and performance boosts, a process the author says will continue as frameworks evolve. The piece suggests that a future Ruby release could deliver tenfold speed or memory improvements, making a rewrite unnecessary. In short, LLMs amplify the value of the current stack rather than nullify it.
What practical advantages does Rails retain?
Rails offers instant code reloading, eliminating compile‑wait times. Developers can use a REPL to experiment, inspect data, or run scripts on the fly. The author points out that these features let coding agents iterate quickly, a workflow LLMs often exploit. Seeing the code also lets humans spot decisions the model missed, preserving accountability. The combination of live reload, REPL access and a well‑documented ecosystem means teams can move faster without sacrificing control, a benefit the author finds absent in a Rust‑only approach.
Frequently asked questions
Does Ruby on Rails still provide value with LLMs?
Yes. The author says frameworks still give structure, security updates and performance gains, and LLMs can use those same abstractions to improve code.
Is rewriting a Rails app in Rust advisable?
The source warns that a full Rust rewrite introduces new decisions, potential bugs and extensive testing, making it risky for user‑facing applications.
Can AI make a Rails app faster without changing its language?
According to the author, prompting an LLM to “make it faster” can optimise the existing code while preserving behavior, and dependency updates bring free performance improvements.
In a world where AI can draft entire applications, the real competitive edge lies in the scaffolding that keeps those drafts reliable. Rails delivers that scaffolding, continuously refreshed by community updates and tooling that speed development without sacrificing stability. As long as users depend on nuanced behavior, a blind rewrite into Rust risks alienating them. The pragmatic path is to let LLMs enhance the existing stack, not replace it.
Sources: Hacker News – Does Ruby on Rails still make sense? – https://tech.dirkjonker.nl/does-ruby-on-rails-make-sense/