JCrete2013:Polyglot JVM; Scala, Clojure, Groovy; Kotlin

some raw notes:

Write about PolyglotJvm here.

Andres Stay on the server but more dynamicity. very close to Java readability closure runtime-metaprogramming

Uberto: Used Groovy, hard to get into „idiomatic Groovy“

Michael: Why do we do polyglot? Scala’s parser library fighting with compiler speed people issues: getting developers to write idiomatic code

Is closeness to Java a good thing?

Kotlin (Dmitry) more expressive. difference to Ceylon: compatibility with Java. Collections are the standard Java ones with clean „interfaces“

Dmitry
 * Ceylon forks the java-compiler and re-uses backend.

Ignasi: good for testing / „playground areas“

Chris R.: class compatibility is key.

How close should interoperability be?
 * compiler-phase plugins
 * circular references between an arbitrary number of languages?
 * modularization

Microservices or monolithic integration? only on green-field. Juergen: also brown-field.

IDEs.
 * Umberto: light-table for clojure / javascript
 * Andres: Idea
 * debugging is harder