[Larrikin]

Dare I say Google embracing and pushing Kotlin on the Android ecosystem was the last good thing I can remember Google doing. The language is such a joy to to work in without the pitfalls that come with Scala

[tadfisher]

I don't know, Compose is fantastic as well. The way the runtime, foundation, and UI libraries are layered make it a breeze to extend, and the layout system is the only sane one I've used. Overall Compose is a paradigm shift that is too-often compared to React, Flutter or SwiftUI by those who haven't written code using it.

[Larrikin]

Our dev team is looking to switch as soon as we have time to learn it. I assumed it was going to be like React from the one tutorial I've done of it so far, which already excited us.

Is this the best resource for learning it well enough to come out with your opinion that its even better? https://developer.android.com/courses/pathways/compose

I'm also a little worried about missing components currently available in XML, although I know you can mix and match, but not sure how that actually is in practice.

[ianlevesque]

The one time I had to mix so far, to display a CameraX preview view, it worked fine.

[acjohnson55]

They each have their place. Kotlin is super Java. Scala is it's own thing, in a similar sense as Clojure or Groovy.

[NaturalPhallacy]

As someone with a lot of java experience and a small taste of scala, what are the pitfalls that Kotlin avoids?

[argestes]

implicits

[pmarreck]

That is because only masochists use Scala