-
Scott Burton 3.63
Description:
Users want a responsive web app, but that twisted mess of Javascript you wrote is impossible to maintain. A new crop of client-side MVC frameworks are a good way to start untangling it, but watch out: there are strong opinions, broken promises and loads of boilerplate code ahead.
In this talk, we'll look at three popular choices: Backbone, Spine and Ember. What problems do they solve, and which do they introduce? We'll cover core concepts, determine strengths and weaknesses, discover some useful patterns, and find out which is right for your project.
Comments on this Talk
Tim Tyrrell,
12 Aug 01:26 PM
Good job comparing the frameworks. although the issues with Ember.js made me wonder if it was the framework or the speaker ;)
I'm sure Yehuda Katz would have been spitting mad if he were in the audience to hear the Ember part. But even if the speaker failed to make the app work with Ember, the demonstration of the bits of code that were supposed to work were enlightening in explaining the Ember approach versus Backbone.
My biggest "complaint" with the talk is that it left me wanting to have the comparison extended to Knockout, Angular, and the other commonly-referenced MVC JS frameworks. Also, I was wishing to see some examples of libraries that were mentioned in passing which help address some of Backbone's need for boilerplate - but that would have been outside the scope of the talk.
Nice overview and comparison