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.

18

u/f2u Feb 22 '15

I am one of those bleeding edge developers you mention, I know Lisp, ML, Haskell

  • Lisp: 1960

  • ML: 1979

  • Caml: 1987

  • Haskell: 1990

It's funny that those are considered bleeding edge. And I picked the year of the first formal publication. In reality, even Haskell is several years older than the mature (read: old-fashioned) Java.

6

u/BobFloss Feb 22 '15

I guess it's more that those languages have seen increased popularity (and changes, probably) recently.

2

u/llogiq Feb 22 '15

Well, at least Haskell has changed quite a bit since the first release. Even Rust, which is pre-1.0 has been there for some years.

Sorry, but Clojure, Ceylon and Kotlin, while being nice, bring no dramatically new ideas to the table.

1

u/yogthos Feb 23 '15

Clojure takes many great ideas from Haskell and makes them accessible to regular developers. It's dramatically new for most people and most importantly it's usable right now on a mature platform.

2

u/llogiq Feb 23 '15

So you're saying I can skip clojure, because I already grok Haskell?

1

u/yogthos Feb 23 '15

If you find yourself productive using Haskell and get to use it professionally then sure. That doesn't appear to be the case for most people though. :)

I think the fact that Clojure runs on the JVM is a huge advantage in terms of practicality. A lot of companies already use Java and there's no technical barrier to introducing Clojure.

You can keep using same tools, same IDEs, same CI, and deployment environment. The only thing that changes is the language you're using. On top of that you can continue to leverage the existing code you have using interop.

2

u/llogiq Feb 23 '15

Interop doesn't stop at the JVM level. I for one have some coworkers who only know Java (and perhaps a bit of Fortran here or R there).

On the other hand, Java devs usually make up for the productivity loss imposed by their languages by (mostly) refraining from language navel-gazing on reddit, hackernews, etc. :-)

→ More replies (1)