Is Ruby on Rails Maintainable? 348
kale77in asks: "I've become a big fan of Ruby over the past few months, but I'm not at all sure about Ruby On Rails. Automatic code generation sets of alarm bells in my mind; so that, to RoR's promise of 'Web Development that Doesn't Hurt', I automatically add '...until you have to maintain it'. On the other hand, some writers and coders I respect (like the Pragmatic Programming mob) seem to be fans. I've mainly written generators in Python, to produce PHP/SQL/Java from SQL files, but I've always gone back to well-constructed objects, where extension and overloading offers more precise and maintainable customization than auto-generation allows. So is Rails just a nice RAD tool for disposable, cookie-cutter apps (which have a place, of course)? Is high-level generation just a bad OO substitute? And what has your experience of Rails' maintainability been?"
We've been told... (Score:3, Funny)
Re:Uhm... (Score:2, Funny)
No, but interpreters have always slowed me down.
Nobody even uses the scaffolding anymore (Score:3, Funny)
Re:Yes, very (Score:5, Funny)
If you think Ruby on Rails is scary... (Score:3, Funny)
Doesn't work. (Score:4, Funny)
Sadly, the stupid are shameless.
Re:Yes, very (Score:3, Funny)
No, the key is to have a superficial language feature that has no impact on development time but keeps people away.
Tons of parentheses seems to work well. Using indentation to delimit is another approach that's still in its infancy.