DISQUS

@mitchell Thanks for your vote. I agree that they're all very good frameworks. Personally, the syntax of "resource_controller" appeals to me. There's a reason I think things need to shake out a little bit: as the rails community grows, there will be more developers who work in teams with others who have different backgrounds.

If I were to land on a team with three other developers, it's possible that each of us might know the nuances of a different framework. I'd bet that the team would burn a lot of valuable time picking a DRY controller framework, instead of writing useful code. Then 3/4 of the team would have to spend a few hours learning the new conventions.

I predict that one of these frameworks will eventually be folded in to the Rails framework itself.

On an unrelated topic: How do you know Brent?

Hahaha. No: I quit my night job.

Funny thing is, we strongly considered rails for our portal app 3 years ago. Rob talked us out of it. Imagine that.

Kinda puts things in perspective to hear him say, "it covers about 40 or 50 years" of his career. That's a lot of content.

@nathan Incidentally, so do I. The other few have benefits, but I started with m_r and know it the best, so I've stuck with it.