11–20 of 41 posts
if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case
and my question is, is there any jvm language which is faster than java
is the plan for koltin to replace java in the development of jetbrains products if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case and my question is, is there any jvm language which is faster than java
is the plan for koltin to replace java in the development of jetbrains products if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case and my question is, is there any jvm language which is faster than java
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.
is the plan for koltin to replace java in the development of jetbrains products if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case and my question is, is there any jvm language which is faster than java
is the plan for koltin to replace java in the development of jetbrains products if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case and my question is, is there any jvm language which is faster than java
is the plan for koltin to replace java in the development of jetbrains products if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case and my question is, is there any jvm language which is faster than java
is the plan for koltin to replace java in the development of jetbrains products if yes, then i would assume the primary objective should be performance .. but this doesnt seem to be the case and my question is, is there any jvm language which is faster than java
I questioning if that is the fault of the language, the jvm, or the developer at this point.
Still no more than "coffescript for java".
While the new features look great, I still can't help but feel like there's a lot of redundancy compared to things that are already commonplace in Scala. Fast forwarding 2 years, I think Kotlin will still be catching up with where Scala is today, and Scala may have migrated to Dotty / 3.0 by then. Of course, there's still plenty of room for both languages, and I'm sure Kotlin will introduce interesting innovations of…
Kotlin has things Scala doesn't, like efficient optionality in the type system, and better Java interop. These are things that the Scala guys probably aren't interested in adding, and likewise, the Kotlin guys don't want to add some things that Scala has, like implicits. So thinking of it as a one dimensional line isn't really correct. Kotlin and Scala overlap in many ways, but the ways in which they don't (and will…
Honest question - what is it that makes Scala's optionality inefficient compared to Kotlin? I'd never heard of this before.
This is awesome news. yield-return semantics was something I missed dearly. Note that we’re still in the process of estimating the effort needed to implement this feature, and we don’t know whether it would be reasonable to support it in the 1.1 timeframe or it would be postponed to a later release. :) I can already tell you: yield is probably doable, async-await will have to be postponed.