> Thus, getters and setters should not be encouraged. Damn, so why are they encouraged in Java? 11 out of 10 frameworks insist that you write getters/setters s

> Thus, getters and setters should not be encouraged. Damn, so why are they encouraged in Java? 11 out of 10 frameworks insist that you write getters/setters so properties can be accessed from outside. Java designers need to get more practical. If getters/setters are unavoidable, I'd better have them without so much boilerplate in my code. No need to go the C# way. Just enough to avoid repeating the name and type 3+ times each would be great.