Hi Howard, >From the recent discussion, I am coming to an idea: Is it your vision to bring the Ruby language features to Tapestry? For example, duck typing (vs explicit interface implementation), dynamic type checking and typeless variables (vs compile time checking), metaprogramming, mixin, closure, etc? Is there anything in the Java language that you would like to keep more than those in Ruby?
If this is the case, can one summarize this strategy as writing Java code in the surface, but Ruby code in the essence? Or do you consider Ruby more suitable for doing Web UI than Java but Java is better in business logic, so Tapestry is used as a bridge to integrate the two worlds? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
