News for hackers. Stuff that matters.
Re:Kotlin Post-1.0 Roadmap by lmm on Thursday April 14, 2016 @11:46AM (#11497632)
All JVM languages "are" the same speed, because they compile to the same bytecode.

OTOH some languages make it more practical / cheaper to write higher-performance code, e.g. in Scala you can use @specialized to automatically generate unboxed special cases for generic code that you'd have to write (and keep track of) by hand in Java. But if you ask "in which JVM language is it most practical/cheapest to write feature X with performance Y?" then the biggest component of the answer is going to be how easy programming in general in that language is, not anything specific to performance.

The question "how fast will a naive implementation in language X perform?" does have an answer, but it's not a question you should ever be asking - if a naive implementation in language X is faster than a naive implementation in language Y, but takes 3x as long to write as an optimised implementation in language Y that's faster than the naive implementation in language X, then language Y is the better choice.

Re:Kotlin Post-1.0 Roadmap by gregschlom on Thursday April 14, 2016 @12:47PM (#11498266)
They compile to the same bytecode, but some languages may have features that compile to a lot more bytecode than others. A dynamic language such as Clojure, for example, is definitely slower than Java, although they are both JVM-based, because it has to do a lot more.
Re:Kotlin Post-1.0 Roadmap by mike_hearn on Thursday April 14, 2016 @01:21PM (#11498647)
Kotlin relies quite heavily on bytecode level method inlining, for instance.

The advantage is that it makes code written in a functional style effectively free (well, almost, unless you could gain performance from step fusion). The disadvantage is that the JVM wasn't designed for that and it messes up stack traces.