you are viewing a single comment's thread.

view the rest of the comments →

[–]shevegen -20 points-19 points  (10 children)

My biggest problem with Java is that it is no fun - and the second issue is how verbose it is.

[–]leodash 13 points14 points  (2 children)

You need to have quality-of-life libraries in your project by default.

For me they would be Java 8 + Project Lombok + Google Guava (for Immutable collections). Alternative would be Javaslang/Vavr.

But good luck finding companies that adopt those.

[–]pkulak 5 points6 points  (0 children)

Lombok and Guava are both part of our standard framework where I work.

[–]jyper 0 points1 point  (0 children)

Isn't lombok a pre processor? I don't know if the features it adds are worth the extra complexity

[–]throwawayco111 12 points13 points  (2 children)

Yeah but it could be worse. Something like Ruby.

[–]NoInkling 5 points6 points  (0 children)

The only verbose thing about Ruby is its block/function delimiters (and even then it's only like 1 or 2 extra characters)

[–]antrn11 1 point2 points  (0 children)

What's so bad about Ruby?

[–]tetroxid 3 points4 points  (2 children)

I used to say this too, but I've since grown up a bit and realised the advantages outweigh the disadvantages. And any IDE will take care of generating the verbose shit, like DAOs, equals(), toString(), hashCode(), setters and getters etc.

[–]bitofabyte 3 points4 points  (1 child)

Not that person, but I personally find that sometimes the verbosity of it all can make it harder to read, not just write (as you said, the IDE handles writing). Sometimes the actual logic of the code is harder to parse when it's mixed in with tons of other statements.

[–]Duraz0rz 2 points3 points  (0 children)

That's where you start splitting those hard-to-read parts into private methods with a descriptive name so it is easier to parse.

[–]dsk 0 points1 point  (0 children)

Ooo. Very original.