Getters/Setters. Evil. Period

yegor256.com

7 points·yegor256a··3 comments

That was...a rather empty article, especially considering the argument was supposed to close the issue. While it is interesting to change the point of view from data manipulate to object/system manipulation the author managed to lose that point inside a religious naming debate.

When the "big reveal" of an article is to change the name of a method and then say "look how clever this is!" it becomes hard to take it seriously.

You're not the first to comment like this (see the comments below the article). I was surprised to see how many people pay too little attention to naming of variables, methods and classes in object-oriented programming. I strongly believe that a wrong name can play a key role in a good design, as well as a bad name can ruin the entire project.

Yeah I actually went back and looked through that comment section afterwards. The responses from the author were super disappointing.

While I agree that the naming of variables is vastly more important than some (most?) people think, tossing convention without any actual rules for what should replace it is pretty worthless.

The immutability argument was actually novel to me and something that I actually found to be an interesting shift in thought process. However, the change from: Ball ball = dog.getBall(); to: Ball ball = dog.give();

totally destroys any readability. Give returns an object? That object is a ball? What?

Reply on news.ycombinator.com