I've been doing Rails now for over a decade (!) and in some sense I agree with DHH that Ruby is good enough. However I think it's also unavoidable that the Ru

I've been doing Rails now for over a decade (!) and in some sense I agree with DHH that Ruby is good enough. However I think it's also unavoidable that the Ruby language is designed in such a way that there is a performance ceiling that will be impossible to break through, and that we will increasingly feel that pain of that ceiling as applications get more complex. I still love Ruby, but there is a lot of interesting developments that are catching my eye just as Rails did so many years ago. It's important to remember what the web development landscape was like in 2004. PHP, Perl, ASP and Java are all weak languages which I would never choose over Ruby. These days things are condierably different. While I have no great love for Node, there are clear benefits to isomorphic client/server code, and going async-first across the board. Similarly whether it's Go, Rust, Elixir, Clojure or Haskell, there is significant community traction in languages that have order-of-magnitude better performance characteristics, and solve problems of both parallelism and type safety which pay huge dividends in performance and maintainability over time. I still think Rails is hard to beat for rapid prototyping, and I'm not in a rush to jump ship, but I think DHH is kind of sticking his head in the sand here. Once upon a time it made a lot of sense to pay Ruby's performance tax in exchange for the power and expressiveness of the language, these days I think we're seeing the ascendancy of languages that show you can still have great expressiveness while sacrificing much less in terms of performance, parallelism, and safety.