I tried Kotlin for some time and went back to Java. Kotlin is nice, and on some days preferrable, but the fact of the matter is, it's really not that much more

I tried Kotlin for some time and went back to Java. Kotlin is nice, and on some days preferrable, but the fact of the matter is, it's really not that much more legible or succinct than Java in the long run. Look at Androind BTE docs [1] - the K vs. J examples side by side, there really isn't that much difference. In the end, I feel K is just a 'different flavour' of Java, and often I feel that the makers of K are just throwing a bunch of ideas together, without necessarily having a philosophy. Given a choice between a 'world of J or K' - to me, it's kind of a toss up - but in reality - J is the incumbent. You have to know J and deal with J at every step, all sorts of libraries are in J etc. etc. - so in reality, the offer of Kotlin is really not Kotlin, it's always Kotlin+Java - meaning two languages and paradigms to support. If this were 1996 and we had to pick between DVD and BlueRay, it would be a difference decision, but in the end, it's not really 'either or', it's J or J+K. In the end, J is not that much more hard to write and the differences are negligible except for some specific things ... so I've switch back to J and don't miss K. [1] https://developer.android.com/guide/topics/connectivity/bluetooth#kotlin https://developer.android.com/guide/topics/connectivity/blue...