When used intelligently, Rails concerns are great - Code with Jason

There seem to be two main camps regarding Rails concerns. One camp says concerns are good. The other camp says concerns are bad.I don’t buy this dichotomy. To state what ought to be obvious, not everything is either good or bad.I’ll make a small digression to illustrate my point, using the example of a knife.You could use a knife to stab me in the leg, or you could use a knife to whittle me a magnificent wooden sculpture.Or, if you weren’t too familiar with knives, you could try to use a knife instead of a spoon in a misguided attempt to eat a bowl of soup. (Then you could write a blog post about why knives are terrible because you can’t eat soup with them.)You get the idea.I want to discuss where concerns might be a good idea and where they might not be. In order to do this it might be helpful to start by articulating which types of problems people tend to use concerns to try to solve.
When used intelligently, Rails concerns are great - Code with Jason #ruby #rails #rubyonrails #bosnia #programming #tutorials #rubydeveloper #railsdeveloper

Nezir Zahirovic

Freelance software developer Ruby On Rails (6 years) / MCPD .Net / C# / Asp.Net / CSS / SQL / (11 years)

related articles