What is the argument for using ES6 getters and setters over getProperty/setProperty convention?

Question

class Foo {
    getName = () => this.name;

    setName = (name) => this.name = name;
}

and

Answer 1

There aren't any specific things you can't do with getMethod() and setMethod(), but it allows for different code styles. For instance you could, with a get foo and set foo, write:

obj.foo++;

which would call the getter then the setter. You could, of course, have the set function then validate that the value is within a specific range, for instance. The traditional code would look like:

obj.setFoo(obj.getFoo() + 1);

You cannot distinguish between a direct property access and method access.

That's kinda the point. I'd argue that if something is really expensive, you just shouldn't use getters for it.