I actually prefer this model of code generation to abstracting everything away into the plugin where I can't get at it. I generally do a lot of modification to

I actually prefer this model of code generation to abstracting everything away into the plugin where I can't get at it. I generally do a lot of modification to code in plugins, and having it generated and hackable right away is much easier to me than having to hunt it down, hack it in the plugin, dig through the plugin's tests, fix the test there, and then hope it didn't break anything else. Of course, if you're not skilled enough to be doing that sort of modification or your apps are simple enough it doesn't call for it, then that's no win for you. But even so, to say the code that restful_auth generates is nasty either betrays your ignorance and/or shows that you tow some party line that I've never been privvy to. The code it generates is perfectly fine. It was written by Rick Olson, who (as I well know) is a fantastic developer. It doesn't support tons of extra bells and whistles like Clearance and friends, but who really needs a lot of the stuff they offer in every app? It's deadweight. In fact, depending on which branch you get of the restful_auth plugin, the code it generates abstracts stuff away in modules that you include (so you don't have to go through that oh so cumbersome maintenance you seem so caught up on) and it generates all the stuff you'd have to create by hand for Clearance.