3 ms·
I'd say databinding is useful for smaller convenience plugins, not for the architecture of larger JavaScript applications. From my quick skim this book is spot
by niels 14y ago
I'd say databinding is useful for smaller convenience plugins, not for the architecture of larger JavaScript applications. From my quick skim this book is spot on.
- heretohelp 14y agoIt is your opinion that the answer to making a larger JavaScript application is one big bucket of state Object? Tell me you've got something better than that.
- zachrose 14y agoSort of? I mean, if you're using models and collections to store _model and collection_ state, then essentially yes, you'll probably have a global variable that namespaces the state of data in your application (or closure-wrapped modules, as the author suggests). At a certain point (and fairly early, really) keeping the state of an interactive application as HTML nodes is not what I want.
- pfraze 14y agoOr a number of isolated, small state objects with well-defined interfaces.
- danso 14y agoSeriously? So you think Backbone.js and the like are just a fad?
- heretohelp 14y agoI'm not fond of the way Backbone.js works. It solves none of the hard problems of making an SPA. (AngularJS is guilty of this too, albeit from a different angle.)