I just built a site that had two parts. A public viewable part and an
admin part. The public viewable part all got changed but with the
admin part, the client was happy to save the money and just go direct
with scaffold generated pages. They did everything the client needed
for this simple application and it saved me time and them money.
I think many people use the scaffolding just to get underway. I
think it works fine for that and a bit more than that. For instance,
I put a website together for me to track my time spent on client
projects. I don’t need anything fancy for adding clients, adding
tasks and adding projects, so I use the scaffolding for that.
BUT…to quote from the Agile Web Dev book - “scaffolding is not
meant to be the shake and bake of website design”.
Just my two cents worth.
PS. Just developed another website this weekend and have to say that
Rails is a marvel. I was drawn into rails through that video you
refer to, but since I have met the product in more depth, I am more
impressed rather than less. Rails is a thing of beauty and
scaffolding is a useful tool.