4 ms·
+1 on this. I'm a Ruby contractor and never use scaffolding, and in general I tend to eschew anything that generates a lot of code. Although, this is probably
by sjtgraham 15y ago
+1 on this. I'm a Ruby contractor and never use scaffolding, and in general I tend to eschew anything that generates a lot of code.
Although, this is probably useful to those with not much Ruby/Rails experience.
- gouravtiwari21 15y agoI think as community is growing there are more people turning towards RoR from other technologies, because: 1. Ruby is language of developers 2. With Rails building application is pretty fast. I think I have attended a session 4 years back (when I was nuby) when one guy taken user requirements and generated rails app in few hours through scaffolds (and I must tell you it was very inspiring). Though it was just a skeleton and not at all production ready, but at least gives sponsors a feel of application what they envision and in turn they provide quick feedback. So, I think scaffolds are still useful to provide you bunch of useful files, which otherwise you write by hand.
- tptacek 15y agoScaffolds are a fine way to learn the Rails conventions, but in several years of doing security assessments in the codebases of some of the world's largest Rails apps, I have never once noticed one being used. Professional Rails developers seem to shun them as a rule.
- danenania 15y agoI think that most of the spots where scaffolding could be useful to experienced devs, a higher level abstraction that does its generating at runtime is much better. It can be difficult to get right, but you end up with more power, better reusability, and less code to maintain overall.