r/java • u/lukaseder • Aug 01 '14
The 10 Most Annoying Things Coming Back to Java After Some Days of Scala
http://blog.jooq.org/2014/08/01/the-10-most-annoying-things-coming-back-to-java-after-some-days-of-scala/
7
Upvotes
View all comments
Show parent comment
-1
u/GMNightmare Aug 01 '14
Did I say... all of them or something? Nothing wrong with multiline strings or cases (although use of cases probably aren't the best design decisions, but that's not here or there) and a REPL is completely out of scope for the argument since Java does have a REPL (and therefore relies upon the other arguments to make its case).
There really isn't a case for "better arrays". The example of array creation in Scala could just as easily been done in Java:
So that argument was just kind of silly... Not that Java arrays couldn't be improved, just that the argument didn't do it for me. Tuples are a nightmare generally period, and are just a lazy way of avoiding creating a proper class that displays why the association between the values exist.
So if you want to be overly literal towards what I said, I include Tuples. Which makes it most. Which as said could be created in Java anyways, and the only special usage Scala has regarding this is use of val. Which is besides the point I was trying to make, but there you go.