3 ms·
No issues with choosing Java (used it for years), but I would argue that OO and reflection aren't great reasons for specifically choosing Java.
by davelnewton 10y ago
No issues with choosing Java (used it for years), but I would argue that OO and reflection aren't great reasons for specifically choosing Java.
- AnimalMuppet 10y agoTo get that specific set (OO, reflection, garbage collection), what would be your choice?
- jsmeaton 10y agoI'd choose C# over java, but I recognize that java currently has a better cross platform story.
- davelnewton 10y agoJust about any other OOP language. I don't find reflection itself to be particularly helpful, e.g., the only times I used it in Java were during low-level framework creation and code generation. Anything else is better handled via interfaces or similar functionality. But if I were forced to use the JVM (which is a nice platform) I'd tend towards Clojure (distinctly not OO). If OO was a strict requirement then Groovy or Scala. Java's OOP implementation, however, is fairly limited in scope, although Java 8 has somewhat alleviated my own particular pain points (e.g., lambdas).
- vorg 10y ago> I'd tend towards Clojure. If OO was a strict requirement then Groovy or Scala Use Scala for building systems that actually require the OO structure. Use Apache Groovy for glue code and tests, and other scripty stuff like build scripts for Gradle.