What About Rails?

The summary is exactly why a lot of people is upset.

>That’s what bothers me most. I’m skeptical of his AI claims, but that’s not the real issue here.

>The problem is that he stood up at Rails World and told everyone that he was moving his product off Rails and the best thing he could come up with to say to people still using Rails was that we’re “the best of the best.” Thanks, I guess.

>Maybe Rails is done, in the way the Mosscap project claims. Maybe it’s time to focus on stability and maintenance. If that’s the plan, someone needs to say it. If it isn’t, then let’s hear about where we’re headed. DHH did neither.

While I mostly agree with DHH's take on this particular technological cycle, this is a very well thought out criticism.

Rails, or even more so php have VERY little to bring to the table in 2026 going forward. Rails (ruby) is still a saner language than PHP, but as slow as php is. (granted ruby is not idiotic like PHP and runs rather than start/die).

If you go the LLM route something like Go is probably the goto default for MOST networking/web-first apps. You get static types, and a fast compile cycle (rust is still very slow here), and IF you want more from the language you can use something like Lisette (https://lisette.run/).

Bottom line is dynamic languages are obsolete. There is really no benefits from using them outside very small throw away scripts.

From the talk it’s clear, Rails needs to be forked.