Re:Returning to Rails in 2026
by tianrking on Thursday March 12, 2026 @08:07PM
(#47359058)
I think the real divide isn't typed vs untyped, it's what replaces the safety net.
In statically typed ecosystems the compiler catches a lot of mistakes.
In Rails ecosystems the safety net historically became tests + conventions.
The problem shows up once the codebase gets large and those conventions start to drift. At that point the compiler would have been a very useful backstop.
That's probably why a lot of long-time Rails developers still love it for small teams and product work, but feel friction once the codebase crosses a certain size.
In statically typed ecosystems the compiler catches a lot of mistakes. In Rails ecosystems the safety net historically became tests + conventions.
The problem shows up once the codebase gets large and those conventions start to drift. At that point the compiler would have been a very useful backstop.
That's probably why a lot of long-time Rails developers still love it for small teams and product work, but feel friction once the codebase crosses a certain size.