3 ms·

Free your mind. Drop all that getXXX setXXX Java-esque noise. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/get https://develope

Free your mind. Drop all that getXXX setXXX Java-esque noise. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/get https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/set https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... http://es6-features.org/#Proxying http://es6-features.org/#Proxying Otherwise, yeah, I can hardly make heads or tails of most "self documenting" (i.e. - undocumented, per SOP) static typed code.

BinaryIdiot 10y ago
> Free your mind. Drop all that getXXX setXXX Java-esque noise[...] You confuse my statement. I was not referring to things that should be meant as synchronous properties. These are methods that do more like make an AJAX call to a server. Those that return promises or take in callbacks would be awkward or impossible to force into a property or proxy. I was merely referring to the act of making code as obvious as possible for its intended outcome.
- Roboprog 10y ago
  Gotcha. Sorry about the tangent, as you were primarily discussing grokking what the names of things were doing anyway.