News for hackers. Stuff that matters.
Re:Rise and fall of JVM languages by izacus on Monday August 21, 2017 @06:17AM (#15063383)
Probably because it was built to seamlessly interoperate with existing Java code and targeted JVM 6 compatibility (it was built to make development of IntelliJ IDEs simpler which had to run on Java 6 VMs and which already had a lot of code written in Java).

As such it turned out to be a natural fit for Android apps as well, because the platform has pretty much the same type of limitations.

Other nice things: - Standard library is tiny so you don't get a large app size and method count hit. - The datastructures are fully interoperable with Java ones so calling out to existing Java libraries and code feels completely natural. I need to stress how important this is - you can just drop Kotlin classes into existing codebase and things will just work and look natural. - The language itself it very easy to pick up - it fixes A LOT of Java pain points, but it doesn't really try to change fundamental paradigms. Which means that pretty much any Java developer can quickly become productive in it. - The IDE support it superb and practically on the same level as Java. - The compiler is fast enough and good enough.

Re:Rise and fall of JVM languages by vram22 on Monday August 21, 2017 @12:51PM (#15065857)
>it fixes A LOT of Java pain points

What are the pain points it fixes?

Re:Rise and fall of JVM languages by dionian on Monday August 21, 2017 @05:28PM (#15068005)
null