Comments on: Why Ruby’s Mixins Gives Rails an Advantage over Java Frameworks

By: Ruby mixins as shown on cars | Kai Richard König

Ruby mixins as shown on cars | Kai Richard König — Thu, 30 Jul 2009 17:35:34 +0000

[...] Juxie ( i dont know the authors name ) last but no least you can read Rob Di Marco’s article Why Ruby’s Mixins Gives Rails an Advantage over Java Frameworks [...]

By: Nathan

Nathan — Tue, 14 Jul 2009 16:28:15 +0000

The one thing Ruby and Rails folks fail to take into account is the complexity that mixins add when the shit hits the fan. Trying to backtrace a problem through a complex Rails application when some automagic in a mixin has failed is quite possibly the most painful programming experience EVERRRRRR!! And I’m comparing this to memory leaks in C++.

By: mark

mark — Sat, 04 Apr 2009 01:12:09 +0000

The problem with the Java folks is that they point out to scala and groovy, but ultimately fail to admit that Java does not allow anything like adding behaviour as easily as Ruby does.

SomeClass.send :include, NameOfModule

That’s it. One line of ruby. Screw the “with great power comes great responsibility”. If this simple feature confuses you, perhaps you should stick to the great world of Java.

It is a bit strange to compare Ruby to Java though – comparing it to groovy, scala or python may be a lot better, because Java is very different.

By: Cristian R.

Cristian R. — Thu, 02 Apr 2009 10:52:53 +0000

Very nice article. Thank you for making the issue of Mixins in Rails so clear.

By: Steve L

Steve L — Wed, 01 Apr 2009 18:40:41 +0000

@Jesse and @Rob (I guess)

“”"
I would so f-ing love if java could have mix-ins. Itâ€™s impossible and it canâ€™t as itâ€™s so totally a dynamic language kind of thing but man that would be so f-ing nice
“”"

How would you compare Scala’s traits w/ Ruby mixins. I feel like it’s rather similar, and Scala isn’t dynamic (in the “typing” way, which is I think is the way you are using it here).

Scala Traits:
http://www.scala-lang.org/node/126

By: Justin

Justin — Wed, 01 Apr 2009 15:30:12 +0000

And with great power comes great responsibility

— fires web over evil doers –

The mixin is very powerful but, as with Objective-c, the runtime modification of classes, either via replacement or addition, can lead to confusion as to how certain functionality is achieved.

Initially the flexibility of said features can be intoxicating but abuse can be problematic.

Interestingly, it is exactly this condition that lead Jane St Capital to adopt a functional programming language (OCAML), which allows them to determine behaviour explicitly without tracking n modules.

I am not saying that it is not a powerful feature or that you should not use it but some caution is needed.

By: Ruby Mixings with extend and include | Kai Richard KÃ¶nig

Ruby Mixings with extend and include | Kai Richard KÃ¶nig — Tue, 24 Feb 2009 19:22:48 +0000

[...] Juxie ( i dont know the authors name ) last but no least you can read Rob Di Marco’s article Why Rubyâ€™s Mixins Gives Rails an Advantage over Java Frameworks [...]

By: PHP 6 traerÃ¡ “traits” | JAVA

PHP 6 traerÃ¡ “traits” | JAVA — Fri, 05 Dec 2008 17:24:37 +0000

[...] Ventajas de los Ruby mixing frente a Java. [...]

By: PHP 6 traerÃ¡ “traits” | orientada a objetos

PHP 6 traerÃ¡ “traits” | orientada a objetos — Tue, 29 Jul 2008 09:03:09 +0000

[...] Ventajas de los Ruby mixing frente a Java. [...]

By: Programación en castellano. ¿Ruby on Rails está muerto? programacion gratis

Programación en castellano. ¿Ruby on Rails está muerto? programacion gratis — Thu, 13 Mar 2008 21:07:53 +0000

[...] como argumento trozos de código.Una orientación a objetos total. Realmente poderoso.mixing: es otra forma de reutilizar código. No es exactamente herencia múltiple, si no [...]