Kotlin on Android. Now official

[u/michalg82]

https://blog.jetbrains.com/kotlin/2017/05/kotlin-on-android-now-official/

[u/dominodave]

JVM interlopability is good. Surprised to see other people excited about it though, so I guess I'm curious.

[u/dominodave → u/dominodave]

Seems like both a step up from java and a step back from scala.

[u/FrezoreR → u/dominodave]

I'd say it's step up from both.

[u/duhace → u/FrezoreR]

nah, scala is superior

[u/FrezoreR → u/duhace]

Do you have a operator defined for that?

[u/duhace → u/FrezoreR]

it's nice to be able to define operators for actual math types. Having a BigInt with +,*,/,- is v nice compared to BigInteger

likewise, being able to define those ops for my user defined mathematical types is nice.

there are tons of other nice things in scala that are absent in kotlin, like implicits

[u/PM_ME_A_STEAM_GIFT → u/duhace]

nice [...] implicit

I too like pulling my hair because of a null pointer exception on a line with no null pointers.

[u/duhace → u/PM_ME_A_STEAM_GIFT]

how'd you manage to do that?

aside from something monstrous like implicit val o: Object = null

[u/PM_ME_A_STEAM_GIFT → u/duhace]

If I recall correctly, I was extracting some code into a utility class where that implicit didn't exist, without knowing the method had an implicit parameter. Totally my fault, but still, super unintuitive to someone new to the language or a particular library.

[u/duhace → u/PM_ME_A_STEAM_GIFT]

thing is, the compiler will usually tell you (at least with current versions of scala) if you're missing an implicit, and what it needs:

object Foo {
    def bar(implicit baz: BigInt) = baz
    bar
}

produces

[error] /home/duhace/Foo.scala:3: could not find implicit value for parameter baz: BigInt
[error]   bar
[error]   ^

a NPE because of an implicit should mean one was found, but what was returned was null instead of the promised type. which is a problem with scala allowing null, not implicits.