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

219

u/aldo_reset Feb 22 '15 edited Feb 22 '15

Why do many software engineers not like Java?

They don't.

Seriously, I know it might be hard to believe, especially if you spend time reading reddit, HN or if you are subscribed to a few mailing-lists on the subject (which means you are part of a very tiny minority), but the bottom line is that the majority of Java developers is quite happy with Java.

If you are one of these bleeding edge developers who keep their knowledge current, are aware of Scala, Kotlin, Ceylon, Clojure or maybe even ML or Haskell, you are convinced that Java is an abomination and that certainly, all its users must absolutely hate it. And you are dead, dead wrong about that.

Before Java, we had C++, and if in the 1990-1995 period, you had interviewed C++ developers, you would probably have found out that a huge proportion of C++ developers absolutely hated programming in this language. Which set the stage for Java to take over in 1995.

I'm not seeing this today. There are no rabid mobs of developers with pitchforks massing at the gates and asking for a revolution. Java is respected for its productivity, its readability and its unbeatable fast path to getting things done in a way that's scalable and maintainable.

Which is why that it's not going to be replaced any time soon. Not by Scala, not by Kotlin, not by Ceylon. In a lustrum, maybe. But not in the near future.

Java is fine, it's liked, it's respected (for good and bad reasons) and it's going to be around for a very, very long time.

40

u/llogiq Feb 22 '15

I am one of those bleeding edge developers you mention, I know Lisp, ML, Haskell and am currently looking into Rust. And I'm also a Java developer, and quite happy with Java.

Java sucks at some points, yes, but not as hard as many think. For a lot of problems, it's actually quite capable, and the specific pain points some folks never tire to mention either can be worked around with little effort or don't impair productivity as much as they think anyway. Also, frankly, the tooling just rocks.

1

u/BeforeTime Feb 22 '15

Java has classes and objects. You'd be looking long for a more powerful abstraction mechanism than that. Other languages might have more abstraction tools that are more suited to some situations, but objects can almost always get the job done. Other mechanisms are just more terse, which can be valuable, but they are not strictly speaking more powerful.

What Java lacks is some sort of syntactic abstraction such as e.g. macros or haskells handling of two argument functions.

3

u/alloec Feb 22 '15

Java has classes and objects

In Java context those two are more of less same thing. I think you mean interfaces and objects and it is an okayish abstraction mechanism, but not exactly powerful.

Am I wrong to assume you don't really understand other abstractions other those found in OOP nowadays? Because terseness in the non-oop abstractions you refer to are not the strengths of these abstractions.

→ More replies (3)