So here's a question - I want to start (or restart?) a discussion on
the role of scaffolding. Should I do that here, or in Talk? I'm
inclined to say here, since it would (hopefully) have a noticeable
impact on core... and given that, I'll go ahead and say my piece (and
just repost it to Talk if that's the consensus).
As it currently stands, scaffolding is broken. We all know it's not
production-ready code (unlike, say, Django's), and it doesn't really
educate new users in the best practices of Rails development (it uses
for loops, has insufficient testing, etc.) I think these two distinct
goals have made life more difficult for loads of people - from new
Rails devs picking up less-than-optimal habits, to contributors who
keep submitting patches to make scaffolding more solid (and to the
people who +1 or reject those patches).
My proposal, then, is to separate these goals. Refocus scaffolding on
providing solid, usable code, and accept patches that move it closer
to that. Instead of just abandoning the educational aspects, however,
split them out and address them in a downloadable sample application
that is designed to teach best practices - something like the caboose
sample app (though that hasn't been updated since May, I think). I
think this will go a long way towards meeting both goals - scaffolding
will be more useful, and new developers will have a focused sample
application to learn from.