now but the new Ecmascript 5
specification picked it up
as well. Properties that are actually functions.
It's a feature
that PHP introduced with their object oriented approach and I'm sure many other languages have it.
The thing is; in PHP, you already don't really know what the hell is really going on behind the scenes. I'll name "arrays" and leave it at that. Google for the workings of arrays to see what I mean.
With these getter and setter properties you don't anymore. And that annoys me because they're mostly syntactic sugar. You don't save a function call by using them but do introduce a whole new complexity layer to the language.
And don't get me wrong. I can think of a few fun uses for them. Heck, I can see it being used, clearly. But aside from some edge cases (using external json without using jsonp), it's mostly syntactic sugar because it won't do much you couldn't otherwise already do.
I've felt this way for a long time and I know this. If you're a programmer working with me on a project or, god forbid, under me on a project, you'd better have damned good excuse for using this feature.