Which is exactly what makes Rails 4 and 5 a reasonable choice for slow-moving projects on a budget (i.e. no money to pay for massive library updates every N months).
I think the vocal early adopters are going to jump ship, if they haven't already. But I'm more likely than ever to start new projects on Rails.
Of course, if there's anything in particular that you are missing from Rails, then the lack of fundamental changes can be a showstopper.
*edit: For clarification, I use Ruby every day and I think its awesome! However, I don't want to see it lose popularity the way Pearl did. I'm concerned that if the language doesn't continue to innovate and improve, that I will lose ground. Lots of new languages have similarly great ergonomics, but get concurrency right, or are faster. I don't think improved concurrency is really on the table for Ruby 3, so I think 3x3 is going to be critical to the long term future of the language.
But, that's just my prediction and its likely wrong.
http://engineering.appfolio.com/appfolio-engineering/2015/11...
https://blog.heroku.com/where_will_ruby_go_now_talking_with_... https://www.reddit.com/r/ruby/comments/3tje5a/ruby_3x3_ruby_...
It's the same reason you'd never find a modern CPU without multiple layers of caching.
That said, I'd call it a fundamental architecture requirement (and one you can't really avoid anyway), given fundamental limitations imposed by the speed of light.
I don't know how mature it is, but couldn't jruby be the answer to this?
Smart money at this point seems like a significant portion of the Rails community could begin moving to Elixir/Phoenix over the coming years. The advantages from a language/VM level just look impossible for Ruby to overcome, along with a blub effect kicking in.