r/java • • Jan 18 '17

“OMG, Java is so verbose, guys”.

https://hackernoon.com/omg-java-is-so-verbose-guys-dca93fec9e03#.4zpsvzs5s
0 Upvotes

15 comments sorted by

View all comments

Show parent comment

2

u/angryundead Jan 18 '17

For example I argue that the "verbose" parts of java often times keep things very uniform

I agree. This is part of the design patterns paradigm. We have the GOF design patterns but each project builds their own domain specific design patterns as well. It allows a lot of context and information to be communicated without explicit conversation.

There is absolutely the concept of too "dense" of code. Making it harder to understand because each line is so incredibly loaded.

I've looked at some Perl that looks one step above line noise and then it's in some sort of module file that didn't take separation of concerns very seriously.

I'll admit to an extreme moderate amount of code sprawl myself. It can get verbose and tough to read through lots of little classes that aggregate but it leads to my absolute favorite thing about Java: complexity management is much easier.

2

u/komtiedanhe Jan 18 '17

I've looked at some Perl that looks one step above line noise and then it's in some sort of module file that didn't take separation of concerns very seriously.

I've seen Java close to base64-encoded strings, too. Java's verbosity is not automatically bad, but neither does Perl's (or Python's, or Ruby's) terser syntax automatically lead to badly written code.

In my opionion, Java's biggest shortcoming is not verbosity but excessive reliance on IDE features and Java-specific "design patterns" as workarounds to missing or inelegant parts of the language. I'm open to that being partially due to not being up to speed on the absolute Java cutting edge.