I think Rails 3.x continues to live up to that gospel. You're right that Rails 3 is more complicated than Rails 2 (although it is also much cleaner than Rails 2), which was more complicated than Rails 1. However, the world of web development is also steadily more complicated. There was a time when knowing how to create a webpage with CSS put you at the forefront of web technology. That time is long gone.
From a general use perspective, Rails has always been designed with a focus on intuitiveness and trying to eschew unnecessary configuration. Whether it succeeds on both fronts is a matter of opinion, but considering the types of configuration options it provides I think the team has done a pretty good job.
Rails is a pre-built web app architecture. Of course it is always going to be quicker and have less of a learning curve to just throw together your own simple app architecture from scratch. But if the app you're building isn't trivial, in most cases it's going to save you a lot of time (in not reinventing the wheel or getting caught in common pitfalls) to go with the prebuilt time-tested community-supported architecture.
I wouldn't think Rails compares too poorly to the PHP MVC frameworks. Sure if you're building just a simple sort of website with maybe a few forms go with framework-free PHP, but for more complex but somewhat standard web apps if you forgo the framework (for Ruby, PHP, etc.) it is usually a mistake.
There are a number of frameworks that meet those requirements now, including Rails. My point was that Rails has a real problem now in that it is a framework that fewer want to spend the time to learn, in my opinion and the opinion of others that make their living writing Rails apps. I see very smart people and people I work with (not necessarily, but sometimes mutually exclusive ;) ) promoting technology these days that doesn't fit the requirements I stated above for a framework/language/tool that will serve the test of time. That bothers me.
If you are really looking for a suggestion, I say go to the following URL and start comparing frameworks. This will at least help give some indication of usage. Then go to the forums, mailing lists, etc. and see whether things are getting more or less active over time: http://www.indeed.com/jobtrends
So while he may make money on Rails geeks that continue on and with those that want to learn, there are fewer that are coming on and will come on now then there were.
If you like Rails, listen to Ryan. I've been doing RoR a while and really, really appreciate the Railscasts (and the Asciicasts of his Railscasts- thanks Eifion!). But if you are looking for a long-term framework to stand by, keep looking.