IMO, the best value of scaffolds is writing custom ones for common tasks in your own application. I've done this on a number of occasions. It's easy and I think it's a quite under-utilized feature of rails.
While basic CRUD is probably better delegated to engine's now. the core concept in scaffolds seems to be that setting up an app quickly and taking the busy work out of building common things that need to be hand customized. Even an engine for admin UIs will have boilerplate. So why not combine these two approaches? TL;DR Don't throw the baby out with the bathwater. Chris Eppstein On Thu, Mar 8, 2012 at 11:09 AM, richard schneeman < [email protected]> wrote: > Anecdotally I can remember a few times I was glad, scaffolds existed > like when teaching Rails classes to beginners, and having them excited > to get started so quickly. I can also remember more than a few times I > regretted using a scaffold after having to heavily remove or modify > most of the code it generated. Rather than lean on either of these > sets of experiences, is there some way we can test and validate that > this would make using rails for beginners easier in the long run? > Serious question. I'll be happy to A/B test-teach this to a group of > students if we could come up with some reliable way of measuring > success. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rubyonrails-core?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
