5 ms·
Java on Android is a miserable experience because of how far behind it is. That you can't really guarantee that anything past Java 1.7 is available means that e
by saagarjha 4y ago
Java on Android is a miserable experience because of how far behind it is. That you can't really guarantee that anything past Java 1.7 is available means that everyone just writes to that lowest common denominator (of course, there's plenty of legacy code too…)
- pjmlp 4y agoYes, how else would they push their Kotlin agenda, if modern Java was given the same access. See how little everyone cares on the JVM, it is just another guest language alongside Scala, Clojure and Groovy competing for attention.
- jraph 4y agoI don't really understand your comment. - What do they win by pushing Kotlin against Java (for reasons that are not also beneficial to developers)? The word "agenda" makes it seem like they have evil intents - Doesn't Kotlin depend on the JVM, and so wouldn't it benefit from an upgrade - Isn't Kotlin a programming language that uses the JVM and the Java standard library anyway? (I saw a bit of Kotlin, I contributed a small patch to QKSMS, it seems it is a bit like Groovy in that it is an alternative syntax but is essentially Java with some syntax sugar and some additional classes to make some tasks easier) I understand that Kotlin may not directly benefit from the new Java language features, but it seems like it would benefit from all the other advances. (I'm not defending Google, I don't like them)
- re-thc 4y agoKotlin is a safety net because Google/Android vs Oracle (the lawsuit).
- pjmlp 4y agoNot really, because Kotlin is useless without JVM ecosystem. InteliJ/Android Studio, Gradle and Maven Central libraries. Kotlin/Native was so well done that they had to reboot the effort. If they cared about so much, they should have migrated to Dart instead.
- re-thc 4y agoIt's just a diversion? We're using Kotlin and not Java? The fact that Kotlin uses Java is then Kotlin's problem (so to speak).
- imtringued 4y agoI don't see Groovy competing for attention. People who want to have a Rails like development experience on the JVM is a completely different market than the usual Spring Boot stuff or legacy code that still uses xml hibernate definitions. Yes, I still have to deal with that. Also the Java codebase is significantly slower because raw Hibernate is terrible and should never be combined with JSF. Meanwhile with grails your only performance worry is that each field plugin template is its own class, which puts immense pressure on the class loader which has to do the non envious job of loading a thousand classes. Despite significant amounts of indirection and excessive use of hidden reflection to abstract over entity/domain classes, the parts I expected to be slow are never the ones you would expect. CompileStatic, etc is almost never worth it. Groovy competes more with Ruby than with Java.