Thanks for your comments.
I'd vote NO. Scaffolding isn't about providing a cross-browser solution with graceful degradation.
Perhaps not, but isn't it better to have applications that do and to
promote graceful degredation?
And even if the scaffolding doesn't get changed, the code to support a
delete action by default would still be a good thing, rather than
adding a collection to each resources route.
It's about giving you a temporary structure you can lean your app against while building it.
Most of my code still uses scaffolded controller code (only added
lines to it, didn't take away).
By the time you want to launch the app, scaffolding should be replaced by code you built yourself.
For the views and tests, sure. But the base of the model and
controllers likely stay the whole way through app development (at
least, this has been the case with a project I'm working on at the
I don't have anything against doing things the way you propose, but I'd rather scaffolding stay as minimal and simple as possible.
When it comes down to it, it's only 3 controller lines and a view
Every line of code in the scaffolding bears a maintenance cost
Shouldn't be much though right? How often does the scaffolding code
change per release since 2.1?