5 ms·
The JVM and tools + libraries built around it are great. Java itself is trash, IMO - I really don't see any reason you'd want to write Java instead of Kotlin. S
by s4vi0r 9y ago
The JVM and tools + libraries built around it are great. Java itself is trash, IMO - I really don't see any reason you'd want to write Java instead of Kotlin. Saves you the hassle of boilerplate, introduces plenty missing features/improvements, runs on the JVM and on Android as well, and switching over is trivial.
- pjmlp 9y agoThere is no JVM without Java, your precious Kotlin code needs Java to run on the JVM, and to make use of all those nice libraries written in Java. Even more so when Hotspot finally gets replaced by Graal, as long term plan on the Java's future roadmap. Likewise on Android, yes Kotlin now has official support, but AOSP Framework code is still Java and it will stay like that for the years to come.
- zaptheimpaler 9y agoI would prefer writing Scala/Kotlin over Java. I still don't think that merits calling Java "trash". I am perfectly happy writing Java. Boilerplate & a few null-checks are very far from the truly horrible things about bad software - they are minor annoyances. This hyperbole about language is really not helpful. On the scale of things that make code good or not, separation of concerns & modularity, documentation etc. are 10-100 times more important than language.
- peterashford 9y agoI've been playing with Kotlin a bit recently. I really enjoyed it until I started coding some stuff in earnest and discovered that I still find Netbeans & Java more productive than Idea & Kotlin. The issue with boilerplate in Java is overblown - IDEs just generate all that stuff. Calling Java trash is pretty offensive IMO.