Much more concise. I was curious on Jeremy's view on getters, setters in JS - can be summed up as it is "impossible to reason about the side-effects of your co

Much more concise. I was curious on Jeremy's view on getters, setters in JS - can be summed up as it is "impossible to reason about the side-effects of your code" (aside from the fact that it also does not work on IE). http://irclogger.com/.coffeescript/2011-01-05#1294280074 http://irclogger.com/.coffeescript/2011-01-05#1294280074 How is that different than the validation / error handling in the model set method in Backbone.js (in that they can run arbitrary code)? Is it just the distinction of side-effects in the language vs the framework? Also, why should a = obj.b need to be any more predicable than a = obj.b()? It seems like there are benefits to using getters / setters (ie, http://ejohn.org/blog/javascript-getters-and-setters/ http://ejohn.org/blog/javascript-getters-and-setters/), and I actually think the syntax is cleaner "get firstName" vs "getFirstName". Curious to understand more about the objection.