|
I've been using Backbone at Earbits (YC w11) [1] since February and have been very happy with it. We're running a pretty complex AJAX app that streams music along with providing a large set of functionality around the music itself (artist info, local concert alerts, track history, deep facebook integration, bookmarking favorites, event logging, running contests and promotions and so on). For an idea of scale, we have:
~60 backbone views,
~120 javascript templates (underscore jst),
~30 backbone models + collections,
1 controller (the router) And we have a fairly complex system of white-labeling that allows us to swap out javascript templates and augment view functionality for partner sites [2] and local sites [3] without adding a lot of overhead. The combination of Backbone + Underscore + Jammit with Rails/Rack on the backend is working great. Even developers who are not familiar at all with Backbone and the ajax app, can dive in and understand everything pretty quickly. Can't possibly recommend it highly enough, if you
1) are comfortable with Javascript, and
2) prefer to roll most of your own code so that you're not beholden to bulky rigid frameworks. There are some quirks that annoy me, but overall I can't complain. One of these days when I have some more free time, I'll try and write a series of posts explaining how we're using it and our key learnings. [1] http://earbits.com
[2] http://sfgate.earbits.com
[3] http://la.earbits.com |