Catalyst creates routes, just like Rails.
Could you elaborate on that? Maybe I didn't understand what routes are then. I am aware that all frameworks map resources to some kind of action, function or method, but the way they do this, as well as the flexibility, are what matters. Does Rails have a pendant to what Catalyst calls a Chained dispatch type? Does it have an equal potential as uri_for at his hand?
I think C::A now has routes, but I'm not sure about Catalyst.
I think you mean "Rails-style routes" here, because otherwise this would contradict your first statement.
I've spent time trying to figure out why my Catalyst routing wasn't working.
Again, no idea what "routing" means in Catalyst sense. You mean your actions weren't found under the locations you expected? I usually just check the debug output and see where my error was :)
To my mind, Catalyst truly is the best of both worlds - I have the power of CPAN married to the power of Rails.
I can understand that. Though for me, nothing in Rails really appeals to me. My design decisions (or environmental constraints) mostly don't conform to what DHH sees as the right way to do things. And my being more comfortable with Perl syntax than the Ruby one (they're not that different, but it's the small things) is one of the reasons I never really used Rails. Other than that: Full Ack, Catalyst is the best :)
Ordinary morality is for ordinary people. -- Aleister Crowley