![]() However, down the road, there is a good chance you will need some of those. Yes, many of those stuff may not be useful or necessary at the beginning of the project life-cycle. For example, logging utility, csrf protection, session encryption, etc. Besides, many stuff are built in the framework. Many will work well together out-of-box, for example devise and cancancan. For example, they are all designed with same naming convention. But thanks to that, many of the gems are coded with it in mind. Rails is a very opinionated framework, there're pros and cons to it. So Just go with the prepackaged toolkit then. And looks like you are not building some next-gen super duper fast smart application. Given that you are the only dev on the project, I'd assume that the resource is fairly limited. Of course, at times DIY toolkit can do better on specific tasks. Whereas, node.js with whatever backend framekwork of choice, is like a DIY toolkit assembled by mix-and-match different tools in a large tool shop. Rails is like a prepackaged toolkit, which can get most of the common tasks done fairly with ease. I'd use the following metaphor to non-technical people.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |