25 ms·
I'd still pick Java. You don't even need to use Java as your language: just something that targets the JVM. If you want compatibility, performance, ubiquity, l
by smt88 5y ago
I'd still pick Java. You don't even need to use Java as your language: just something that targets the JVM.
If you want compatibility, performance, ubiquity, language choice, and ecosystem, there isn't really a better option than the JVM right now.
- muzani 5y agoKotlin?
- smt88 5y agoMaybe. I think you need something with the syntactic flexibility to work well with different types of data. I would have to look closer at Clojure and Scala.
- muzani 5y agoIt's almost exactly the same as Java, but much more compact. Java fans say Java has evolved to match Kotlin and they're probably right. But it's just faster to type ? instead of @Nullable.
- smt88 5y ago> Java fans say Java has evolved to match Kotlin and they're probably right. It definitely adopted a lot of the good things in Kotlin, but Kotlin doesn't have the problem of needing to maintain backward compatibility. Kotlin doesn't even natively have null, which (in my opinion) is the best thing about the language.
- sshlocalhost98 5y agoYes java ftw