You can use batman.js with any backend!

Batman.js’s prevent and allowAndFire make it easy to fire a callback when you’re finished working on the members of a Batman.Set.

Batman.js objects (Batman.Object instances) have properties defined with @accessor. These properties are cached until one of their sources busts their cache.

If the batman-rails gem isn’t an option, gulp.js is a good candidate for compiling batman.js apps for production.

A Batman.Model has a lifecycle object that fires events on the record when it’s being dirtied, cleaned, loaded, saved or destroyed.

Batman.js provides a powerful model associations inspired by Ruby on Rails. But, if you’re loading child items from ids, it’s not going to work out of the box.

Just a few things I’ve picked up about Batman.RestStorage and Batman.RailsStorage.

Living a day at a time sounds a bit like lazy enumeration.

When working on HTML for Batman.Views, it can be annoying to refresh and navigate back to wherever you were. Hacking into Batman.HTMLStore enables you to reload HTML without refreshing

Need to add a header to an ActiveResource request? If you need to do it at dynamically at request-time, redefine .headers.