> It's led me to ask the question "If Rails isn't good enough, then why are you using it?"
That's a pretty poor question. Rails is a framework, and for the most part it works. However, that doesn't mean it's the one and true way of doing things.
Granted, I generally agree with the article. Helpers are a step backwards.
The sole purpose of a helper is to keep code out of templates and presentation out of controllers.
How could they do a better job of that than they do now?
Remember, the article you're agreeing with says that helpers are bad because they are "just functions". This is, in a word, crazy. It's one thing to design with objects; it's another thing to turn all your functions into classes so you can pretend you're OO.
So put the code in the model, where it belongs ... I rarely use helpers for anything but formatting-fu - everything else is in the model. I rarely use helpers, period.
