DISQUS

Nathan Weizenbaum · 1 year ago

I use make_resourceful... but then again, I'm biased.

peteonrails · 1 year ago

@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.

Mitchell Blankenship · 1 year ago

Personally I use resource_controller. Like you Peter it's the one I started with first and have become accustomed too. Seems to me though when it comes down to it you can't go wrong with any of them. I think it's better to have options especially when all the options mean cleaner more efficient code.

peteonrails · 1 year ago

@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?

Nathan · 9 months ago

Good god, I'm trying to work out the same thing. I'm definitely leaning toward resource_controller because it just seems to be most logical correct way to do it plus the author appears enthusiastic and intelligent. It's hard to figure out which of this new rash of plugins are still supported or how much longer they will be worked on, which will prosper and eventually which one will make it into core Rails.