We used a similar approach with Bones (https://github.com/developmentseed/bones https://github.com/developmentseed/bones) for a while and ended up dropping it f

We used a similar approach with Bones (https://github.com/developmentseed/bones https://github.com/developmentseed/bones) for a while and ended up dropping it for a more decoupled architecture (API on side and static client on the other). I remember chatting with Spike about this at a Backbone.js meetup at Airbnb's office last year, I think they were aware of the limitations similar frameworks were running into. I'd be interested in seeing how this play outside of Airbnb's use case, but from experience I think sharing backbone.js on both client and server, while neat, end up being pretty constraining.