Why Custom modules as mixins in Ruby? - Purpose & Use Cases

The Big Idea

What if you could fix a bug once and see it fixed everywhere instantly?

The Scenario

Imagine you have several classes in your Ruby program, and each needs the same set of methods like logging or formatting. You try to copy and paste the same code into every class.

The Problem

Copying code everywhere makes your program bulky and hard to fix. If you want to change the shared behavior, you must update every class separately, which is slow and error-prone.

The Solution

Custom modules as mixins let you write shared methods once inside a module. Then you include that module in any class that needs those methods. This keeps your code clean and easy to update.

Before vs After

✗ Before

class A
  def greet
    puts 'Hello from A'
  end
end

class B
  def greet
    puts 'Hello from B'
  end
end

✓ After

module Greeter
  def greet
    puts 'Hello from A'
  end
end

class A
  include Greeter
end

class B
  include Greeter
end

What It Enables

You can share behavior across many classes effortlessly, making your code DRY (Don't Repeat Yourself) and easier to maintain.

Real Life Example

Think of a game where many characters can jump or run. Instead of writing jump and run methods in every character class, you put them in a module and mix it in wherever needed.

Key Takeaways

Modules let you write shared code once.

Mixins add that shared code to any class easily.

This saves time and reduces mistakes when updating code.