For me, there is nothing quite like Kotlin. It is pure pleasure for me. It just makes sense to me in a way most languages can't. Every other language makes me wish I was working in Kotlin. Rust...
For me, there is nothing quite like Kotlin. It is pure pleasure for me. It just makes sense to me in a way most languages can't. Every other language makes me wish I was working in Kotlin. Rust comes close, but comes with the kinds of considerations while coding I could do without.
The vast array of available targets, reusable code between server, client, & various UIs, the simple dependency management for each of them in gradle, extension functions, the lambda function argument syntax, the null safety (and functions on nullable types!), the explicit mutability with immutable as default, very well structured concurrency, the flexibility in writing scripts, batch jobs or services...
There are 3 main blockers to its adoption I think:
People associate it to Java, and while I like Java I know it's not everyone's cup of tea. Communicating how it can be compiled to other targets than the JVM is a challenge.
People (rightfully) associate it with Jetbrains and the heavy IDEs they make. I love them but I see the move towards slim alternatives like VSCode, and while that is no blocker, it makes people doubtful.
It's harder to hire for a relatively unknown language, which makes teams think twice before they go all in.
Personally, the one thing I wish it had more of was control over vectorized/parallel instructions like SIMD or GPU computations. These currently have to be handed off to more native solutions (which is entirely possible for many targets, with native compilation or JNI for instance). I'm hopeful but I do understand it's a bit niche as far as use cases go.
For me, there is nothing quite like Kotlin. It is pure pleasure for me. It just makes sense to me in a way most languages can't. Every other language makes me wish I was working in Kotlin. Rust comes close, but comes with the kinds of considerations while coding I could do without.
The vast array of available targets, reusable code between server, client, & various UIs, the simple dependency management for each of them in gradle, extension functions, the lambda function argument syntax, the null safety (and functions on nullable types!), the explicit mutability with immutable as default, very well structured concurrency, the flexibility in writing scripts, batch jobs or services...
There are 3 main blockers to its adoption I think:
Personally, the one thing I wish it had more of was control over vectorized/parallel instructions like SIMD or GPU computations. These currently have to be handed off to more native solutions (which is entirely possible for many targets, with native compilation or JNI for instance). I'm hopeful but I do understand it's a bit niche as far as use cases go.