Backbone.js, Jasmine and Rails: The Lust Story
summary
A Rails app called Blog Mate moves its front end to backbone and adds jasmine tests, cutting a lot of custom JS and duplicated save/update/destroy code. The concrete win is using the events module so multiple views auto-update without wiring views into models, and switching to backbone models resolves REST syncing and removes manual id/callback bugs that only showed outside development. Tests use jasmine fixtures and stubbed server calls. Result: tighter organization, fewer lines, and working end-to-end single-page behavior.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 3:56Blog Mate project
- 7:05JavaScript challenges
- 9:11Custom patterns limits
- 13:52Backbone.js solution
- 16:42Backbone views
- 17:47Backbone models and Rails
- 21:20Backbone events
- 22:45Backbone collections
- 24:30Testing with Jasmine
- 25:54Backbone routes
- 26:35Why Backbone matters
- 27:37Benefits and future
related talks
40mUsing Backbone.js with Rails: Patterns from the Wild
18mStart using Jasmine. Write better JavaScript. Profit.
28mBuilding in Rails, Backbone, and CoffeeScript
34mYour Front End Framework is Overkill - Server Side Javascript w/ Rails
32mModern JavaScript, without giving up on Rails Jonathan Johnson
40mFRONTEND CHOICES
32mImplementing Rails 3.1...
54mTaking JavaScript Seriously with Backbone.js
