3 ms·
Yes, Java is finally becoming a language I don't cry myself to sleep over. I've still got other languages I (vastly) prefer, but I don't feel like I'm fighting
by Twisol 5y ago
Yes, Java is finally becoming a language I don't cry myself to sleep over. I've still got other languages I (vastly) prefer, but I don't feel like I'm fighting the system nearly as much anymore. (Though, tail-call optimization would mean I don't have to obfuscate so many algorithms that are naturally recursive... it's part of Loom's charter, so maybe after virtual threads.)
- jpgvm 5y agoI prefer Kotlin for a number of reasons but still use Java heavily as it's still a better choice in many places. I think this will be of massive benefit to both languages. Kotlin coroutines will probably be mostly relegated to multiplatform and JS backends but that is fine, server side Kotlin will take full advantage of virtual threads. :D
- aembleton 5y agoWhere is Java a better choice than Kotlin?
- jpgvm 5y agoSo the main thing is libraries. If you write your library in Kotlin then it depends on the Kotlin runtime JARs which seriously bloats it's dependencies. Not a problem where the library is only applicable in Kotlin-land but if it's generally useful from Java/Clojure/Scala then it's better to write it in Java. The other case is general OSS software, Java reaches a wider audience in my field (distributed databases, streaming data, etc). Java is pretty much considered the lingua-franca of Big Data with some very small Scala footprint and much less fluency in Kotlin. I generally write all my own stuff ontop of these on Kotlin but drop down into Java where I need to be able to share things.