The Chicken-and-Egg Problem of Classes and Objects in Ruby (with a Python Twist) 🐔🥚

Hoang Nguyen
Mar 16
3 min read

If you've ever tried to understand object-oriented programming (OOP), you've probably come across this chicken-and-egg dilemma:

Objects come from classes.
But classes are also objects.
So… which came first? 🤔

In Ruby and Python, this isn't just a fun thought experiment—it’s a fundamental design principle that shapes how both languages handle classes, objects, and metaprogramming.

To fully grasp this concept, let’s break it down step by step:

Looking at the Eggs – Objects Are Born from Classes

In both Ruby and Python, objects are instances of classes. Think of a class as a hen that lays eggs (objects). Just like every egg comes from a chicken, every object in Ruby or Python is created from a class.

Defining a Class and Creating Objects

🔹 In Ruby:

🔹 In Python:

From this, we can see that classes exist as blueprints for creating objects. In both Ruby and Python, objects don’t just appear out of nowhere—they are always instances of a class. This seems to suggest that classes must exist first… right? Well, things are about to get more interesting.

Looking at the Chicken – Classes Are Also Objects!

Here’s where the plot thickens. Classes themselves are actually objects! This means that in both Ruby and Python, the class that creates objects is itself an instance of something else.

🔹 In Ruby:

🔹 In Python:

Wait a minute—so a class is also an object? That’s right. In Ruby, every class is actually an instance of Class, and in Python, every class is an instance of type.

This means that the chicken (the class) is also an egg (an object of Class/type). Mind blown? 💥

The Grandmother of All Chickens – Where Do Classes Come From?

If a class is just an instance of another class (Class in Ruby, type in Python), where does that class come from? The answer lies in the object hierarchy of both languages.

🔹 Ruby’s Object Hierarchy:

🔹 Python’s Object Hierarchy:

At the top of Ruby’s object system is BasicObject, while Python has object as its absolute root. The key difference is that Ruby has an extra minimal base class (BasicObject), whereas Python’s object serves as the only root of everything.

Both Ruby and Python follow a similar structure: everything is ultimately an object, even classes themselves.

So, Which Came First?

Now that we understand both sides of the problem, let’s answer the big question:

Did the Egg Come First? (Objects Before Classes)

Every class in Ruby and Python is itself an object.
This means an instance of Class (Ruby) or type (Python) existed before any other class was created.

Or Did the Chicken Come First? (Classes Before Objects)?

Objects can only be created from existing classes.
A class defines the blueprint for making new objects.

The Verdict: Both Came First!

Classes and objects are inseparable—one cannot exist without the other. Classes are objects, and objects come from classes. This makes Ruby and Python two of the most dynamic OOP languages.

So next time someone asks you, “Which came first, the chicken or the egg?”, you can confidently say: In both Ruby and Python, the answer is: Both! 🐔🥚

☕ Enjoying the content? I’d love your support! Subscribe to stay updated, and if you're feeling generous, you can buy me a coffee too! Every coffee fuels more great content. 🚀

Buy me a coffee 🙌