On the client side, you very rarely have access to the entire table -- often you have different slices of it based on different search queries, or associations -- every Book has its own collection of Notes, for example. So just mimicking the Rails-style 1:1 mapping can be a bit of a fallacy.
Also, I recommend everyone read TJ Holowaychuck's latest blog post[1] and lets start distributing these types of things as components instead of "frameworks".
Read the Holowaychuk article. We need to stop working with frameworks and start working with components. How great would it be of I could use Backbone without Events (not picking on Backbone.Events here, just an example), or use a JQuery function that one of my libraries requires without including all 32k of it.
https://twitter.com/illuminations4d/status/22728017176024268...