Cannot agree. Ruby loves its MOP, python loves its method overloads.
Both are highly magic, but a MOP is technically superior to overloads, because you just flip the vtables and don't have to look at every single method call, if some python programmer decided to overload it. Perl has no builtin MOP, and even worse overloads than python.
but the ruby community takes modules to magic extremes. Just take the overload of include vs. extend as one example. Some modules don't even have any reasonable error messages or try to detect when someone stomps on their names or data. It's a madhouse with ruby modules that try to be "magic" or "easy", which is never "simple".
If you ever find yourself pulling back the curtain of many ruby modules, it's time to dig in and swear as you go.
Re:How is Ruby different in Japan?
by setpatchaddress on Sunday June 18, 2017 @11:40PM
(#14584495)
The languages are not very similar. What gives you that idea?
Dynamic types, OO with some extension for functional style, inherited Algol syntax with some homegrown innovations, batteries-included design. Where they differ, it's largely in whether they bend towards consistent style(Python) or more late-binding power(Ruby).
The languages are pretty similar. The community attitudes are different.