Avoid getters and setters whenever possible

Re:Avoid getters and setters whenever possible by davewritescode on Thursday March 22, 2018 @08:03AM (#16647830)

Agreed but immutability can lead to builders and builders lead to lots of code bloat. Plus, from what I've experienced lots of frameworks depend on java bean conventions (i.e. getters/setters for everything).

There's really two missing features of java that could solve 90+% of the use cases for getters/setters.

- Attributes: annotation or keyword based directives for the compiler to generate getters/setters for a given instance variables

- Default + named parameters which would reduce a lot of the pain of multiple constructors and constructors with a tremendous number of parameters.

[ Parent | on HN ]

Re:Avoid getters and setters whenever possible by phkahler on Thursday March 22, 2018 @08:19AM (#16647934)

Instead of attributes that lead to creation of getters/setters, how about the simple notion of private or public access to members? I'm not sure which should be the default, but it sounds like Java programmers would like them private unless otherwise specified. Why add code when all you want is to restrict access?

[ Parent | on HN ]

Re:Avoid getters and setters whenever possible by TheSleeprAwakns on Thursday March 22, 2018 @12:34PM (#16650187)

Lombok (https://projectlombok.org) exists and takes care of the attribute issue you mentioned.

[ Parent | on HN ]