3 ms·
I think the claim there is more like "you can already use the huge amount libraries/your existing code with Java and, with care, you can make your Scala code wo
by emodendroket 10y ago
I think the claim there is more like "you can already use the huge amount libraries/your existing code with Java and, with care, you can make your Scala code work the other way" than "interop is seamless back and forth."
- xaduha 10y agoWell Kotlin does indeed claim that interop is seamless back and forth AFAIK.
- emodendroket 10y agoWhich is neat, but unless you are a library designer it's probably not that much of a selling point.
- xaduha 10y agoMajor selling point is the ability to mix Kotlin and Java freely. I just find it funny how Scala guys are saying "me too" at every opportunity. But that always comes with an asterisk, if you look closely. IDE support is as good, Java interop is as good, etc.
- emodendroket 10y agoSorry, I didn't realize you were personally invested.
- xaduha 10y agoWell I like and use Kotlin, that's the extent of it. Scala is a non-starter for me.
- emodendroket 10y agoHow come? I started using it because my company did and I've found it pretty good, overall.
- xaduha 10y agoI started using Kotlin because the author of MapDB did https://github.com/jankotek/mapdb https://github.com/jankotek/mapdb Scala was around for a long time, perhaps if I could look at it with fresh eyes now I would consider it, but somehow I always had a feeling that Scala isn't for me. And now as Kotlin gaining momentum I'd rather stick with Kotlin. I want first class IDE support and straightforwardness in my workhorse languages. For hobby languages I'd rather play with something like Red or Perl 6.
- emodendroket 10y agoI haven't tried Kotlin but Scala works with IntelliJ pretty well. I'd say it's pretty comparable to VS/R# with C#.
- kodablah 10y agoWell there are still problems there too. Try making a default interface method in Kotlin or invoke MethodHandle's invoke with a specific return type sans casting in Kotlin.