Sign in

A Conservative Case for Rails Concerns

There are many, many articles which condemn the use of concerns in a Rails project, and they all have valid points. I mostly agree with the arguments, such as them causing Bi-directional dependencies and arbitrarily splitting up code into multiple files. That said, I think a lot of these articles go too far by claiming you should never use concerns.

To be clear, if I saw a model that started with 20 concerns being included, I would be… Well, concerned. That’s why I’ve titles this a conservative case for concerns. I think they should be used very sparingly, but not…