On Monday, January 23, 2012 11:34:25 AM UTC+1, raks wrote: > > My new project is the more cutting edge - Java 6(!), MongoDB and the > JVM layer - Java is ok but Groovy is preferred (we use Grails). > > I think polyglot programming will only get bigger and more popular, > > especially as the tooling (IDEs and cross compilers) become better. >
A dynamic language like Groovy can obviously talk to anything, but you loose toolability/interoperability when dynamic invocation is more than just opt-in for a specific subsystem. I'm not sure I see much polyglot in using Groovy to query MongoDB, when the native language is JavaScript. However, it may well demonstrate a more strict nuance of polyglot (semantic polyglot?) that includes type interoperability, which I would consider far superior to having isolated language silos with crude interfaces between them. After all, Neal Fords definition of polyglot represents the way we have been developing programs over the last 30 years or so, and I think we're ready to move on. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To view this discussion on the web visit https://groups.google.com/d/msg/javaposse/-/Ot0nNYxMyLYJ. 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.
