- 5comments
- 338comments
- 4comments
- 93comments
- 114comments
- 201comments
- 46comments
- 36comments
- 365comments
- 563comments
- 145comments
- 26comments
- 11comments
- 359comments
- 398comments
- 129comments
- 14comments
- 4comments
- 52comments
- 37comments
- 22comments
- 624comments
- 22comments
- 127comments
- 17comments
- 12comments
- 21comments
- 39comments
- 11comments
- 50comments
From the talk it’s clear, Rails needs to be forked.
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.
The summary is exactly why a lot of people is upset.