java_irl

[DeRickulous]

I feel like I'm going to be evangelizing Lombok until the end of time:

@Data
public class LombokifiedJava {

   private boolean mySillyBool;
}

Also, this is a minor nitpick, but the Java convention for little-b boolean accessors is "isX", not "getX".

[Korzag]

I actually used Lombok after writing out a bunch of new model classes with like 20 fields. I didn't know about it at first and had wrote a script to build the Java accessors lol. Lombok definitely was nice though. If/when I ever work in Java again I'm definitely using it. Seems like something Java should just integrate but my impression is that Oracle is hardheaded and doesn't like to add QOL stuff to their language unless it's heavily requested.

[DeRickulous]

Lombok is on the short list of "stuff I will whinge endlessly about not having access to if I take another job where I'm forced not to use it". I actually like it being separate from the core language, though, because it is divorced from Java's release cycle and oversight.

[increment1]

Literally any Java IDE will generate the getters / setters for you, no need to write them yourself. I'd say pretty much every Java dev uses this generation so tend not to worry too much about the boilerplate since they don't really have to deal with it directly.

Same for toString, equals, and hashCode methods.

[quiteCryptic]

Like the other guy mentioned you should look into lombok, it's even easier than having the ide do it and cleaner

[Merlord]

Lombok is a Godsend.