I think the idea is that where code in java is equal to or not much longer than its scala equivalent, the java version wins because java is simpler to understand. There also some pragmatic concerns, for example, interopping java 1.1-targeted library code with code written against java 1.6 isn't all that difficult, whereas writing scala 2.8 and using a library written in scala 1.0 is not going to work very well.
On Aug 25, 8:55 am, Kevin Wright <[email protected]> wrote: > http://michid.wordpress.com/2010/08/24/so-scala-is-too-complex/ > > <http://michid.wordpress.com/2010/08/24/so-scala-is-too-complex/>I'm > curious, does anyone have an example of the same problem being solved in > both Java and Scala, with Java offering the simplest solution? > > -- > Kevin Wright > > mail/google talk: [email protected] > wave: [email protected] > skype: kev.lee.wright > twitter: @thecoda -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
