I think, in this instance, the 'immeasurable benefits' should probably read as 'measurable benefits so great they break the scale (but measurably better than th

I think, in this instance, the 'immeasurable benefits' should probably read as 'measurable benefits so great they break the scale (but measurably better than the mess imperative JS creates)'. Recently, especially at a startup I've felt the need to use libraries and frameworks more and more just to hit deadlines and meet the desired user experience. Model binding is a prime example of this: on the web today everything has to be dynamic and reactive. Rather than do something (i.e. animate) and tightly couple the onComplete handler to N other things to do afterwards (via callbacks/promises etc) I prefer to compose my code around n-event subscriptions and react to changes. Thanks to things like model binding (and their frameworks/libraries that offer this) the 'immeasurable benefits' of decoupled and composable functions trump the spaghetti soup reactive Javascript requires. (P.S. one designer is a step up from none!)