Heh yeah fair enough. I find Kotlin infuriating to work in (far more so than many objectively worse languages) because it's such a step backwards from Scala, but if I didn't know what I was missing then I'd probably feel the same way.
I actually used Scala before Kotlin. I get what you mean in Kotlin being less powerful than Scala but for me this has turned out to be a good thing in bigger projects. Kotlin provides enough power to get the job done without giving people too much rope to hang themselves with.
For me it's not about power, it's about consistency. Scala has a couple of general concepts that get applied to everything. Kotlin seems to have a new ad-hoc way of doing every different thing. E.g. my teammate just rewrote some code to use a Scala-style IO type rather than suspend functions because none of us could understand which coroutine context was being used where.
