News for hackers. Stuff that matters.
Re:Why getter and setter methods are evil by touristtam on Wednesday October 08, 2014 @11:22AM (#8427349)
I don't see the point of having a set of accessors on a Ball object from the point of view of a Dog object. It is really up to the programmer to have method names that makes sense in the first place. I don't see how a dog.Weight() makes more sense than the convention dog.GetWeight().

Never the less, I am now intrigued by the book mentioned. :)

[edit] I am curious about the book.

Re:Why getter and setter methods are evil by yegor256a on Wednesday October 08, 2014 @11:50AM (#8427535)
The convention of getWeight() is bad because it assumes an existence of setWeight(). And get/set methods turn an object into a holder of data.
Re:Why getter and setter methods are evil by Rachelgee on Wednesday October 08, 2014 @04:31PM (#8429288)
I don't see the point either. However, the book is the major point of interest in the article. I look forward to read it.