|
|
|
|
|
by osdev
1971 days ago
|
|
I think it’s pretty simple why you’d want to use Kotlin on the server; full stack Kotlin development: 1 language for both Android and Server(lowers time, costs, and you can share code). And Kotlin multi-platform is making good progress, so potentially you can also build shared code for iOS and JavaScript. Again, it all comes down to time, cost, simplicity. Lastly, I have to say, after using futures in Java/Scala, async/await in JS, Kotlin got it right with coroutines, channels and flows. I’m not exactly sure what the roadmap for concurrency looks like in the Java world(even with project loom, etc). While Java is moving fast(finally), I think it’s still weighed down by legacy stuff (nulls, mutable code, lack of expressions and more) |
|