Contents
Why do we not use getters and setters?
Getters and setters expose the private member, and rest the case for their existence on the fact that the private member is exposed. Let’s say I give you only the following API to my Car object:
Why are getters / setters a bad idea in JavaScript?
Besides setters and getters, ECMAScript 2015 (ES6) also comes with proxy object. Proxies help you to define the delegator method which can be used to perform various actions before real access to the key is performed. Actually, it looks like dynamic getters/setters.
Is it safe to use getters in JavaScript?
Of course, you can safely use getters/setters in the environment, which guarantees static type check, but this article is about vanilla JavaScript. This article is my opinion why I think this feature shouldn’t arrive to the vanilla JavaScript in the first place.
What’s the use of getters and setters in Ruby?
Getters and setters are a fake insurance policy of isolated change. One supposed advantage of getters and setters is that on the off-chance that the type of a class member needs to change, the change can be limited to inside the class by making the existing getter simply translate from the internal type to the previously-exposed type.
Is it bad to have a getter in Java?
If you only have a getter, things can be just as bad. In Java at least, returning a reference type from a getter provides that reference to the caller and now it can be manipulated by the caller in unexpected ways. Let me demonstrate. OK, that seems reasonable. I need to be able to see a person’s debts to give them a statement.
When to add getters and setters to OO classes?
First, let me be clear about what I am saying: adding getters and setters to OO classes should be the last resort after considering a series of better alternatives. I believe that a careful analysis yields the conclusion that getters and setters are harmful in the clear majority of cases. What is the harm?