In a world where most programming languages are built to make computers run faster or to make code ultra-secure, one man in Japan in the early '90s asked a different question: "Is it possible to build a language that makes developers truly happy?"

Today, Superdev Academy introduces you to Yukihiro Matsumoto (widely known as Matz) and the journey of the "Red Gem" known as Ruby—a language that doesn't view programmers as mere cogs in a machine, but as "artists" of creation.

1993: Born from a Lack of Choice

Back in 1993, Matz was searching for a scripting language that was as powerful as Perl (which was dominant but had a syntax like a secret code) and more strictly Object-Oriented than Python (which was just a fledgling at the time).

Matz looked for a language that combined Perl's text-processing flexibility with a beautiful, high-level structure. When he couldn't find it, he decided to write it himself on February 24, 1993.

The Naming Story:

Matz and his colleagues discussed gemstone names to follow the legacy of Perl (a homophone for "Pearl"). The two finalists were Coral and Ruby. Ruby won because it sounded more grand, and it happened to be the birthstone of one of his colleagues.

The "Human-Centric" Philosophy: Humans First, Machines Second

Matz firmly believes that "Programming languages should be designed for humans, not computers." Since humans spend thousands of hours staring at code, the language should "anticipate" the programmer's intent—a concept known as the Principle of Least Astonishment.

Technical Insight: "Everything is an Object"

While languages like Java or C++ still have "Primitive Types" (like the integer int which is separate from an Object), in Ruby, everything is truly an object. Even a null value (nil) or a simple number.

• A Beautiful Example: Instead of writing complex loops, you can simply write 5.times { puts "Hello" }. This code prints "Hello" five times. It reads as naturally as English. This "naturalness" is the gift Ruby gives to developers.

MINASWAN: A Culture of Kindness in the Dev Bloodline

What sets Ruby apart isn't just the syntax; it’s the Community. They live by the motto MINASWAN, which stands for "Matz Is Nice And So We Are Nice."

• Started from the Creator: This culture began with Matz himself. He is an engineer known for being incredibly polite, humble, and open to feedback. Because the leader set this tone, the Ruby community became a "welcoming haven" for beginners, focused on friendly exchange.

• Kindness as a Documentation Standard: You’ll notice that most Gems (Ruby libraries) have exceptionally beautiful and easy-to-read documentation. This isn't a coincidence; it’s an expression of care for fellow developers. It’s a deliberate effort to make someone else's job easier.

• From Personality to Performance: The "Niceness" of Rubyists isn't just about being polite—it directly benefits the software:

  • Strong Open Source: When people feel safe to ask questions without being judged, bugs get fixed faster.

  • Limitless Sharing: The ecosystem is filled with "helper tools" designed simply to help others.

  • Global Collaboration: Whether you are a Senior or a Junior, in the Ruby world, everyone is a peer seeking "happiness" in their craft.

💡 Superdev Insight: In other languages, "seniority" might be measured by complex algorithms or execution speed. In the Ruby world, seniority is measured by "how much easier and happier your code makes others." This is why Ruby remains one of the most loved languages in the world, regardless of how much time passes.

Ruby on Rails (2004): The Explosion that Changed Web Dev

While Ruby was beautiful, it was mostly a "hidden gem" in Japan until 2004. That year, David Heinemeier Hansson (DHH) extracted a toolset from his work on Basecamp and released it as Ruby on Rails (RoR).

The Turning Point: "Convention over Configuration"

Rails revolutionized web development by saying: "If you follow the standards we’ve set, you don't need to waste time on endless configuration."

• The Result: Tasks that took weeks in Java or PHP at the time could be finished in minutes in Rails. This is why world-class startups like GitHub, Airbnb, Shopify, and Twitch chose Ruby to build their foundations.

The Evolution of Speed: Ruby 3x3 and YJIT

In the past, Ruby was often criticized for being "beautiful but slow." The team responded with the Ruby 3x3 mission: to make Ruby 3 three times faster than Ruby 2.

• Ractors: A system that allows for better Parallelism without the usual memory headaches.

• YJIT (Yet Another JIT): A cutting-edge technology supported by Shopify’s engineering team. It significantly boosts Ruby's speed in real-world production environments, effectively silencing the old "Ruby is slow" argument.

Conclusion: Why Should We Study Ruby?

Ruby teaches us that "Aesthetics in code" directly impact the quality of the work. When a programmer is happy and doesn't have to fight messy syntax, the resulting code is clean, maintainable, and creative. Learning Ruby helps you see what truly "human" code looks like.

🎯 Stay Tuned with Superdev Academy:

Don't want to miss our deep-dive technical articles and updates? Follow Superdev Academy on all our channels:

• 🔵 Facebook: Superdev Academy Thailand

• 🎬 YouTube: Superdev Academy Channel

• 📸 Instagram: @superdevacademy

• 🎬 TikTok: @superdevacademy

• 🌐 Website: superdevacademy.com