I have to say, the more javascript (these days coffeescript) I write, the more I think an mvc structure on the client is usually a big mistake. Mvc means shared

I have to say, the more javascript (these days coffeescript) I write, the more I think an mvc structure on the client is usually a big mistake. Mvc means shared global state and putting your data behind an inflexible facade, neither of which is necessary or a good idea in ui programming. What's the alternative? Components. Encapsulation. Modularity. It's nothing fancy. Just build small, composable functions and objects that manage their own data and subcomponents, and don't reach outside themselves. In this way you end up building up lots of mini mvcs, one on top of the other, to manage requirements with the approach and data structures most appropriate to each, rather than constantly trying to bend a monolithic global model and api into doing exactly what's needed. You don't need a complex hierarchy of model classes for your data. Just use json. When you need to process or manipulate it, write a function. When you need to send or receive data from the server, $.ajax and handle the result on whichever tier needs it. Send and receive just the data you need in just the structure you need. No syncing or rails-like magic required.