Closed wodencafe closed 2 years ago
Makes this a polyglot project, which has its trade-offs, but I'd sure be happy.
Out of curiosity, what does this mean, if anything, for the prospects of a full Kotlin rewrite? I know some of the llamas crowd has strong negative opinions about Java, and Kotlin might possibly be more attractive to some of them.
If someone is willing to do the work, sure. Or if we want to just compile incrementally side by side with Java and Kotlin. My suggestion would be then to separate the Java and Kotlin into separate subprojects, so that we can have full polyglot cross-compilation, and so that each subproject is aware of the others, regardless of their language. In this scenario, we could have subprojects for each language we can support: Scala, Groovy, Kotlin, Java, Clojure, etc.
I think it makes the most sense to keep the interfaces in Java, in their own subproject, and if we were to rewrite, or if we just want to expand with new logic in other languages, a contributor can implement the interfaces in whatever language they desire.
Thoughts?
I put the polyglot design conversation into issue #8. Merging this.
This adds Kotlin support so that we can start writing files in Kotlin as well as Java.