ROR: To help or not?

Question

I love scaffolding and it is very useful for prototyping. But should we use scaffolding to develop the app as such?

Answer 1

Rails is now called scaffolding (post 2.0). The structure created using the forest generator is more of a basic application, rather than the "prototype" that you selected later.

At least if you are developing your application as RESTful, you will find that you support most of the fishfinder generator created by the controller and model code, adding more logic to them. You could possibly replace the views in the end by storing bits and pieces of Ruby code in them.

Answer 2

There is no harm in using the scaffold to begin developing your application. However, if you are a beginner, you need to understand how you can work without it. Scaffold is a tool for rapid prototyping in rails and can be used if you can quickly change it to suit your requirements.

Answer 3

I use it a lot

i clean using scaffolding, and then gradually replace it with a special code; this is a great way to get something and work pretty fast.

Answer 4

Actually, it depends on your requirements. When we look at the scaffold, it will instantly generate a CRUD (Create, Read, Update and Delete). Therefore, if you need to delete some operations, it is very simple if you encoded it manually. But this can also be done using the scaffold. You just have to remove only these methods. So it is your choice whether you use it or not.

Answer 5

I read several books, the author told me that the developer will not use it in his business project. Therefore, I do not use it in my project at any time. But these are just my options, it depends on you.