Re:Everything that's wrong with Java in a single class
by hythloday on Friday September 21, 2012 @07:27AM
(#4553275)
I don't want to play code golf with you, because I think your point is generally valid, but you can happily and idiomatically reduce the Java method itself to 10 lines with some sympathetic scaffolding from the other classes (this is actually how a lot of code in our game is implemented rather than some theoretical optimum):
The point I'm (perhaps ineptly) making is not that Java isn't all that verbose (because it obviously is) - rather it's that you don't get much of a stack of abstraction by default. If you don't take the time to implement that abstraction, you're going to have a bad time, but if you do, it's not appalling.
[ Parent
| on HN ]
Re:Everything that's wrong with Java in a single class
by rmc on Friday September 21, 2012 @02:10PM
(#4554925)
that, or even 10 lines, is still several orders of magnitude more code than how you do it in a dynamic language like ruby or python
Re:Everything that's wrong with Java in a single class
by hythloday on Friday September 21, 2012 @04:02PM
(#4555473)
It's not really dynamism so much as a functional outlook. Here it is in Scala (probably with a healthy number of syntax errors, and certainly with a whiff of inexperience):
def studentsWhoHaveNotTakenAtLeastOneTest = getStudents.filter{s => s.getTests.filter{t => !t.isTaken}.size > 0}.sorted
You could get a similar amount of code in Java using something like FunctionalJava but that's not really a fair comparison, because patio11 is illustrating Java as it's spotted in the wild, and thus so am I. But with appropriate libraries and implementation patterns you can certainly write concise Java if you so choose.