I will consider Kotlin outside Android, when it becomes relevant for JVM design, being taken into account by all major JVM implementations and JEP proposals, instead of something imposed by an OS vendor, stiffing Java support on purpose.
Guest languages always end up eventually going down their own path.
Not even C++ developed alongside C and UNIX, managed to take over UNIX clones, or industry standards for OS and graphics APIs.
Typescript relevance might wither away when JavaScript gains type annotations, it is after all only a nice linting tool.
Despite all WebAssembly craziness, JavaScript still rules the browser and edge gateways.
It is and you are being very defensive here. Which suggests to me that this isn't the first time you've been challenged on this front.
Dismissing things as "guest" languages maybe steps over the advantages these languages bring. If you had some rational reasons I'd take you more seriously. But you clearly don't. Using big words like "industry standards" doesn't really add to the argument.
> I will consider Kotlin outside Android
Funnily enough the only place I don't use Kotlin is Android. I never did much Android development. I've been using it since 2017 for server side development and the last five years also for browser development (via kotlin-js). It's actually replaced typescript for me. I do a lot of Kotlin multiplatform at this point. I don't recommend this to everyone. But it does work quite well for me as a better Typescript. It still cross compiles to Javascript of course. And lately to WASM if you want to. But the point is, Kotlin is not just a JVM language anymore. People do IOS native development with Kotlin now. With bi-directional swift integration, native libraries, and all the rest.
What things are for and aren't is mostly a mental block on your side. C++ and Typescript are widely used at this point.
> might wither away when JavaScript gains type annotations
If that's so beneficial, you could have been using Typescript for the last ten years.
Big words matter, because there is a whole list of megacorps that rather keep using Java alongside C and C++ to implement their JVMs.
If Kotlin is so great where is the KVM taking over the world, outside ART, when no one is forcing its adoption like on Android?
Actually, is Kotlin Native finally good enough for JetBrains to implement a KVM, without having to rely in something writen in Java with all the related flaws?
I use Typescript where it is imposed upon myself, like Angular and Next.js, when I can have my way of Web development, it is plain Spring MVC or ASP.NET MVC with vanilajs.
My day to day JVM guest language is two decades old at this point and it is remarkably similar to Java and yet none of the latest Java releases have done anything remotely interesting enough that they would make me go back to Java ever.
I will consider Kotlin outside Android, when it becomes relevant for JVM design, being taken into account by all major JVM implementations and JEP proposals, instead of something imposed by an OS vendor, stiffing Java support on purpose.
Guest languages always end up eventually going down their own path.
Not even C++ developed alongside C and UNIX, managed to take over UNIX clones, or industry standards for OS and graphics APIs.
Typescript relevance might wither away when JavaScript gains type annotations, it is after all only a nice linting tool.
Despite all WebAssembly craziness, JavaScript still rules the browser and edge gateways.
If that is irrational, oh well.