3 ms·
For set() and get(), I'm betting its because you can override the handling of attribute accessors on an object--this avoids that confusion.
by angersock 13y ago
For set() and get(), I'm betting its because you can override the handling of attribute accessors on an object--this avoids that confusion.
- masswerk 13y agoOr it could be some kind of "cargo cult" from the implementation in an other language, considering some of the popular writings and discussion in the last time. Personally, I would prefer JS "doing it the JS-way", rather than overloading paradigms by introducing implementation schemes from other languages. (Is JS prone to become a "Frankenstein language"?) I'm hoping you're right with your guess, regarding the motivations behind it.