These days people prefer talking about how they're using node.js or Go.
I have worked with Ruby professionally for 5 years. From my perspective there is more opportunity now then years back, more high quality code being written, more problems can be solved in less time, etc
This is still a very exciting place to be. I have found being good at Ruby has provided the highest ROI of my career.
In DFW, traditionally a dense forest of Enterprisey .NET and J2EE projects, I've seen a LOT of new Rails gigs pop up. A number of startups (growing in this area), but also big companies like Raytheon. I had a long conversation with an Adobe recruiter last year about their Rails initiative, and unless someone can point me towards different information, is it not the case that most web startups default question now is -- "is there a good reason NOT to do this in Rails?"
Rails and Ruby right now feel like Java circa the early 00s or thereabouts, where JVM performance concerns/FUD had clearly been dealt with and pretty much everyone was on board.
My hunch is we may look back on the last couple of years as being a similar tipping point for Ruby/Rails.
As a counterpoint, many people who attend spend their time at camp not doing Rails stuff.
Let's not forget the advancement of JRuby (JVM Ruby), Rubinius (LLVM Ruby), MacRuby (For Native OSX Desktop Apps), RubyMotion (For Native iOS Apps), mRuby (For Embedded Apps).
Not to mention the truck load of conferences every year, the new and existing, accessible and easy-to-use open source projects that are being released and updated frequently.
"Is it just me or has the world moved on from Ruby?".sub("from", "to")
We're doing our best. :)