4 ms·
> Having higher kinded types and type classes like Haskell would be nice though. Don't have to leave the JVM, already there in Scala. And Kotlin Arrow may get
by virtualwhys 6y ago
> Having higher kinded types and type classes like Haskell would be nice though.
Don't have to leave the JVM, already there in Scala. And Kotlin Arrow may get merged into the compiler, so Kotlin may have first class support for these language features one day...
- hedora 6y agoScala uses type erasure to preserve compatibility with the JVM. No thanks. I want the compiler to statically verify my types, and then optimize based on that. At some point, I realized Java code tends to have many more runtime type errors (in particular, NullPointerExceptions and ClassCastExceptions) than similar C++ code (segfaults). Things like rust should be even better than C++, but that’s practical largely thanks to performance optimizations from llvm. Other than Java compatibility, I don’t see any advantage to the JVM at this point.