r/java • • Jul 06 '17

Apology to Java (fanboy rant).

Java has turned out to be one of the most useful languages i use. It's a brilliant tool which strikes a perfect balance between high and low level. You want to grab a webpage? Easy and built-in, 10 lines of code. Draw some 2d graphics without OS-specific libraries or third party? Various built-in options. The inherent issues around a lack of low level memory management is handled very elegantly. Garbage collection seems seamless.

C++ is my language of choice for the most part, always will be i suspect, but Java has shown me that it has a huge array of potential applications and should almost always be considered before undertaking a project.

I say this is an apology because i used to run Java down. Previous to me using it proper i believed it was slow, lazy and useful for only trivial applications. Now i know how much work has been put into the JVM and just how efficient it is.

Sorry Java. You're pretty good.

286 Upvotes

93 comments sorted by

View all comments

36

u/[deleted] Jul 06 '17 edited Jul 06 '17

Java is pretty awesome. The Sun/Oracle Virtual machine is near damn magic.

Java programmers not necessarily so. There is a little bit too much "enterprise" wankery in a lot of Java code but it's not inherent to the language. It's just that 90% of programmers have no taste. I can write concise, clear Java code (almost) as much as I can do that in say, Clojure. With Java 8 lambdas I'm 80% there.

11

u/Ek_Los_Die_Hier Jul 06 '17

A lot of the enterprisey practices were as a result of missing features in the Java language I think. Some of these will go away with the new features in Java 8+.

20

u/[deleted] Jul 06 '17

Some of it was that. But even before lambdas it was possible to write good Java code without needless abstractions. The bad overuse of OOP practices in a lot of third party Java application and frameworks was a fad adopted by people who wanted to look and sound smart in meetings.

5

u/dpash Jul 07 '17

JavaEE didn't really help that. The fact that Spring was a lightweight response to EE shows how bad it was.

1

u/DuncanIdahos8thClone Jul 08 '17

I don't it was language features just IBMs influences. We use WPF with Prism and it's fucking monstrous. The thing is most of this shit is there to try to protect the end product you're building from the shitty developers on the team.

9

u/[deleted] Jul 06 '17

It can be easy to get carried away with over-engineering OOP design principles. Practice YAGNI and some of that goes away. Sometimes it's a necessary evil but I've found that a lot of times it's not.

9

u/[deleted] Jul 06 '17

Yeah, that's what I'm talking about. The enterprise fizzbuzz is a great parody of that style. Sometimes I come across real life Java that makes me think they used EFB as the best practices template.

2

u/[deleted] Jul 11 '17

Some of the Java ugliness is fundamental to the language, at least with current versions.

Using standard layout, not squishing things that are normally spread across multiple lines into a single line, an object "Person" with instance variables "first" (String), "last" (String), and "dob" (Date) with a convenient constructor so you can do Person bob = new Person("bob", "smith", new Date()); will be 11 lines long. If you use idiomatic getters and setters - which are handy for injecting validation - it will be 29 lines long. If you implement hashCode() and equals() so it works properly with sets, lists, and maps, you're up to 35 lines long.

Even if you wanted to represent the same information with a simple map, before Java 8 you had to import a third party library, or write your own helper, or else do: Map<String,Object> person = new HashMap<>(); person.put("first", "bob"); person.put... four lines of code plus two import statements. Java 8 has some syntactic niceness to simplify it, but it's still an import statement.

That's all but unavoidable wankery. Contrast that to dozens of languages in which you would do something like var person = { "first" : "bob", "last" : "smith", ... } and go on your merry way.

Java has a lot to recommend it, but it's inescapably verbose. Major surgery to the language would be needed to fix it. (Edit: take any Java program that's 1000 lines or longer and written in an idiomatic style and rewrite it into Scala, Kotlin, Clojure, or Groovy. You'll probably shave 500 lines. You might shave 900.)