Compiler speed is a fantastic tradeoff. I'm made of meat that runs at maybe 0.0001 MHz after coffee, so I want to offload anything I can to the compiler!

I rather bet in platform languages, without extra layers to debug, FFI and additional tooling not available to all IDEs for the respective platform.

That's a very sensible standpoint.

All of these are technical issues which will be solved by Google eventually, I'm not worrying much about that, they definitely have the resources to make it work.

Kotlin is owned by JetBrains not Google.

And there is Kotlin-Native but the likelihood of JetBrains reimplementing the entire JVM SDK is pretty slim. Not to mention all of the common third party libraries e.g. Guava, HTTPClient.

> Kotlin is owned by JetBrains not Google.

Yes but there's a lot of efforts from Google to support the language as well since now it's the new Android language.

Android supports Java, Kotlin and C++.

Kotlin is just one option more, and the tooling is still not mature as Java.

Specially in compile speed, incremental compilation, debugging, speed in type completion, FFI.

I would not put C++ with the other ones, unfortunately Android has a lot of API only available from Java.

Agreed about the 2nd class status of C++, still that is the official message, about all three languages.

https://developer.android.com/guide/components/fundamentals?...

"Android apps can be written using Kotlin, Java, and C++ languages. "

I bet that in 5 years Kotlin will have as much market as other alternative JVMs languages have today.

And regarding Google, Kotlin is not among the beloved ChromeOS and Fuchsia languages.

So it depends very much on their internal politics.

Is there any official language for ChromeOS?

I believe it supports Most Android and Linux apps now.

Yes, it is called JavaScript.

Android and Linux apps support is made via containers, aka they are not native to the OS, and isn't supported across all Chromebooks models being sold.

And even then, there are support issues.