How did this article get flag killed? I wanted to say something constructive about the topic: Any time you layer an arbitrary UX over a given data model, expre

How did this article get flag killed? I wanted to say something constructive about the topic: Any time you layer an arbitrary UX over a given data model, expressiveness is absolutely necessary in the protocol in order to minimize round trips. This is why SQL has been so successful on the server side. An alternative to the "moving the whole graph to the client side" approach is the intercooler.js way [http://intercoolerjs.org/ http://intercoolerjs.org/]: HTTP requests express UI/UX needs, rather than generalized data queries to support a client-side object graph and model. This eliminates a whole swath of complex issues that come up with managing multiple instances of data in a distributed object graph environment, knocking system complexity down an order of magnitude.