r/programming • • Feb 22 '15

Java Makes Programmers Want To Do Absolutely Anything Else With Their Time

http://www.forbes.com/sites/quora/2015/02/21/java-makes-programmers-want-to-do-absolutely-anything-else-with-their-time/
35 Upvotes

636 comments sorted by

View all comments

Show parent comments

24

u/[deleted] Feb 22 '15

Yes, Java can be more verbose, but that specific example is a very bad argument against it. That's basically how every other strongly typed language did (and some still do) things. Actually, that's not a very good argument either. So, here's more:

  • Polymorphism. The type on the left is what the following code expects to work with. The type on the right is the specific implementation. You could just as easily have Map<String, Set> on the left and new TreeMap<>() on the right. The lines that follow depend on depMap being a map, not a tree or hash map. This doesn't mean much for a silly example like this but in larger systems, it helps in more than one ways. Which brings me to,

  • Self-documenting. If you were able to do it without specifying the type, say something like depMap := getDependencies(), at a quick glance I can't tell what the type of depMap is. On the other hand, Map<String, Set> depMap = getDependncies() tells me exactly what's going on.

  • You don't really have to type it out manually. You'll be using an IDE. If you know how to use your IDE, you will type variable name equals to right hand side, press two extra keys, and let the IDE add the type -- selecting one if there are multiple viable options (because polymorphism).

8

u/ihcn Feb 22 '15

I think the argument is for compile time type inference, something every modern compiled language has, except java of course. Any IDE will tell you what the type is, without you having to type it out.

1

u/[deleted] Feb 22 '15

I mean it's not like it's technically infeasible to infer the type at compile time. The current approach is just a lot clearer (see the second point).

For example, a quick glance while scrolling through the code in a web-based code viewer shows you what type you're dealing with. You don't need to go into an IDE or follow the source code to figure this out. Basically what I'm getting at is that it's a feature, not a deficiency.

Also, IDEs kinda give you coding-time type inference and add the types to the source code for you. So you don't generally have to type it out.

2

u/ihcn Feb 22 '15

I strongly disagree that it's a feature. Java seems to have the mentality that it doesn't give you enough rope to hang yourself with, so it takes away all sorts of crucial features. The ostensible tradeoff is that your code is easier to understand as a result.

But in my experience with enterprise Java, bad developers will write awful code no matter how much you take away from them. The worst codebase I've ever seen, by far, was Java.

→ More replies (2)