# Ruby Mixins vs Rails Concerns

**URL:** <https://www.ruby-forum.com/t/ruby-mixins-vs-rails-concerns/267537>\
**Category:** Rails\
**Created:** [March 7, 2025, 6:30pm UTC](https://www.ruby-forum.com/t/ruby-mixins-vs-rails-concerns/267537 "2025-03-07T18:30:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyMaleh](https://www.ruby-forum.com/user_avatar/www.ruby-forum.com/andymaleh/32/2475_2.png) [@AndyMaleh](https://www.ruby-forum.com/u/AndyMaleh)\
**Post date:** [March 7, 2025, 6:30pm UTC](https://www.ruby-forum.com/t/ruby-mixins-vs-rails-concerns/267537/1 "2025-03-07T18:30:19Z")

</div>

It is amazing how cryptic, difficult to reason about, and expensive to maintain Ruby codebases become when they include countless ‘concerns’ without honoring the Ruby naming convention for mixins as representing “traits”…

Continue reading blog post:

> **[Ruby Mixins vs Rails Concerns](https://andymaleh.blogspot.com/2025/03/ruby-mixins-vs-rails-concerns.html)**
>
> code master oop ruby jruby java jee jse desktop web gui glimmer swt libui tk gtk rails