Actually, I didn't make the claim that Ruby follows the principle of least surprise. Someone felt the design of Ruby follows that philosophy, so they started saying that. I didn't bring that up, actually.

Yukihiro Matsumoto’s quote addresses a common misunderstanding about the design philosophy of the Ruby programming language. He clarifies that he did not personally claim that Ruby follows the principle of least surprise—a design philosophy that suggests software should behave in ways that users intuitively expect, minimizing unexpected behavior. Instead, Matsumoto points out that others may have perceived Ruby’s design as adhering to this principle, which led to the widespread belief. His statement emphasizes that while Ruby’s design may evoke this principle, it wasn’t his explicit intention to label it that way.

The principle of least surprise is important in the world of software development because it aims to create a more user-friendly experience, where the behavior of a program aligns closely with user expectations. Matsumoto’s clarification reveals the way certain aspects of Ruby’s design—such as its simplicity and readability—may have led some to associate it with this principle. However, Matsumoto distances himself from this specific claim, suggesting that the association came more from others' interpretations of the language’s intuitive structure.

Matsumoto’s comment also reflects his humility and thoughtfulness as a designer. He does not claim that Ruby’s design is flawless or strictly adheres to any one principle but instead allows the language’s qualities to speak for themselves. This approach is characteristic of Matsumoto’s work, where he emphasizes developer happiness and creating a language that feels natural and expressive without being confined by rigid rules or expectations.

The origin of this quote comes from Yukihiro Matsumoto, the creator of Ruby. Ruby has become known for its elegant syntax and its focus on making programming more enjoyable and productive. Matsumoto’s response here reflects his understanding that the way a language is perceived can evolve, especially as it gains popularity and becomes a core tool for developers. His clarification about the principle of least surprise illustrates how he prefers to focus on the broader experience of using Ruby rather than adhering to specific philosophical claims about its design.