News for hackers. Stuff that matters.
Re:Kotlin: A New Hope in a Java 6 Wasteland by pjmlp on Monday September 28, 2015 @12:24PM (#10291258)
Besides the sibling answers, the situation will only get worse.

Java 9 brings modules.

Java 10 has on its roadmap value types, JNI replacement, GPGPU support, new array model and whatever they might still consider.

Re:Kotlin: A New Hope in a Java 6 Wasteland by cdbattags on Monday September 28, 2015 @12:26PM (#10291272)
Can you expand on this?
Re:Kotlin: A New Hope in a Java 6 Wasteland by themgt on Monday September 28, 2015 @02:03PM (#10291916)
If you mean the "getting worse" part, I believe the implication is that Google's lack of control over either Java the language, or the Android device ecosystem upgrades, means the future would likely see increasing fragmentation/divergence in important core language features across Android devices, causing much developer pain.

If one assumes e.g. in comparison Apple will in 2 years have 95% of devices capable of running Swift 3 apps vs. 15% of Android devices capable of Java 8, much less 9/10 ... it could be quite a competitive disadvantage for Android, as well as argument for adopting a forward-looking JVM language dedicated to compiling to 1.6 bytecode if you plan to do Android development.

Re:Kotlin: A New Hope in a Java 6 Wasteland by pjmlp on Monday September 28, 2015 @12:37PM (#10291333)
In what sense? These roadmaps have been presented at multiple Java conferences.
Re:Kotlin: A New Hope in a Java 6 Wasteland by AnimalMuppet on Monday September 28, 2015 @06:43PM (#10293692)
I suspect that ctbattags meant "can you expand on why these will make the situation get worse", rather than "can you expand on what these things are".

But I'm not ctbattags, and I'm not psychic, so I could be wrong...

Re:Kotlin: A New Hope in a Java 6 Wasteland by pjmlp on Tuesday September 29, 2015 @05:10AM (#10295242)
I see, then themgt's answer covers it.

From a technical point of it just seemed obvious to me.